# HTTPd Deployment

### <mark style="color:blue;">What's  httpd?</mark>

<mark style="color:orange;">**The Apache HTTP Server (HTTPD): Empowering the Web**</mark>

*<mark style="color:orange;">Apache HTTP Server, commonly known as HTTPD, is more than just a web server; it's the cornerstone of web hosting. Let's unravel the essence of this legendary software:</mark>*

1. <mark style="color:yellow;">**Web Serving Excellence:**</mark> At its core, HTTPD excels at serving web content. It seamlessly delivers HTML, images, CSS, JavaScript, and more to users' browsers via HTTP and HTTPS protocols.
2. **Open Source Prowess:** HTTPD is a proud open-source champion. Its source code is a gift to the world, nurturing a community of developers and fostering innovation.
3. <mark style="color:green;">**Platform Agnostic:**</mark> HTTPD dances gracefully across diverse platforms. It harmonizes with Unix-based systems like Linux and BSD, as well as Windows, offering versatile web hosting solutions.
4. <mark style="color:purple;">**Modular Marvel:**</mark> HTTPD's strength lies in its modularity. With a treasure trove of dynamic modules, it adapts to various scenarios effortlessly. Customize and extend its capabilities as per your desires.
5. <mark style="color:yellow;">**Security Sentry:**</mark> Security is HTTPD's middle name. It comes fortified with access control, authentication, and encryption features, making it the guardian of secure websites. Administrators wield the power to control access meticulously.
6. <mark style="color:orange;">**Configuration Finesse:**</mark> HTTPD's configuration options are as intricate as a Swiss watch. Tailor it to your specific needs by tweaking settings that govern access, performance, and functionality.

*In the ever-evolving landscape of web hosting, Apache HTTP Server stands as a timeless monument, fostering the web's growth securely and efficiently.* 🚀

### <mark style="color:blue;">**How It Works:**</mark>

1. <mark style="color:orange;">**Client Request Unveiled: The Apache Ballet**</mark>

   *<mark style="color:orange;">Behold, the enchanting dance of client requests and Apache's graceful response:</mark>*

   1. **Client Request Debut:** It all commences with a client - often a web browser - extending an HTTP request towards a web server. This request can be as simple as a URL or rich with parameters and information, akin to casting a spell.
   2. <mark style="color:purple;">**Server's Attentive Ear:**</mark> The Apache server is a vigilant sentinel, stationed at a specific port <mark style="color:orange;">(usually 80 for HTTP or 443 for HTTPS)</mark>. It stands ready, ears perked, waiting for the faintest whisper of a client connection.
   3. **Request Unraveled:** As a request arrives, Apache steps onto the stage, armed with its configuration directives from files like 'httpd.conf' or 'apache2.conf.' These directives hold the script, guiding Apache in its response.
   4. <mark style="color:orange;">**Modules, the Dancers:**</mark> Apache's secret lies in its modular ensemble. Each request dictates the choreography. If PHP prowess is needed, the 'mod\_php' module takes center stage, elegantly pirouetting to handle PHP scripts.

   *In this intricate ballet, Apache's modular flexibility allows it to waltz through an array of requests, delivering the perfect performance every time*

### <mark style="color:blue;">Steps And Procedure</mark>

* <mark style="background-color:purple;">**This deployment utilizes the official httpd Docker image. Here's a step-by-step guide to get you started:**</mark>

  1. Begin by navigating to the "Create Apps" page and use the search bar to find the <mark style="color:orange;">httpd</mark> application.
  2. Click on the "Install" button to initiate the installation process.
  3. Fill in all the required fields with the necessary information.
  4. If you prefer, you can click on the "Advanced" option to access additional settings (this step is optional).
  5. After making your selections, press the "Install" button to proceed.
  6. Once the installation is complete, you'll be directed to the "My Apps" page, where you'll find a list of all the applications you've deployed.
  7. Copy the Hostname of the httpd application without the NodePort and paste it into your preferred browser's address bar.
  8. Voilà! You're now able to access the httpd webpage and explore its content.

  By following these straightforward steps, you'll have successfully deployed the Nginx application and gained access to its features through a seamless and user-friendly process.

### <mark style="color:blue;">Installation</mark>

| Docker Image                                                                                                                |
| --------------------------------------------------------------------------------------------------------------------------- |
| [`httpd`](https://hub.docker.com/_/httpd)<mark style="background-color:yellow;">👈(click me,for the dockerhub image)</mark> |

| Application name                                                               |
| ------------------------------------------------------------------------------ |
| <mark style="background-color:yellow;">Eg: httpd1(you can put any name)</mark> |

| Resource Allocation                                                                                                                                                     |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <mark style="background-color:yellow;">0-100%(</mark><mark style="color:orange;">10 % of your allocated resources (CPU, RAM) will be used for this application.)</mark> |

<mark style="background-color:yellow;">`PROTOCOL`</mark>

<table><thead><tr><th width="417">Protocol</th><th>Protocol Value</th></tr></thead><tbody><tr><td><mark style="background-color:yellow;">Http</mark></td><td><mark style="color:orange;">80</mark></td></tr><tr><td><mark style="background-color:yellow;">Tcp</mark></td><td>-</td></tr></tbody></table>

| Install with Default                                                                                                                                        | Advanced                                                                                                                                                               |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <mark style="background-color:yellow;">(select this if you want install with default settings if don't have environment value and working directory)</mark> | <mark style="background-color:yellow;">(select this if you want to go with advanced settings, where you select you own environment value and working directory)</mark> |

If you choose Advanced option:

| ENV VARIABLE                                                            |
| ----------------------------------------------------------------------- |
| <p><code>Give env variable.</code></p><p><code>Eg:key==value</code></p> |

<table><thead><tr><th>WORKING DIR</th></tr></thead><tbody><tr><td><p><code>WORKDIR for the application.</code></p><p> <code>Eg:usr/src/yourAPP</code></p></td></tr><tr><td><mark style="color:red;">Here use ( use the path after   " :"  )</mark></td></tr><tr><td><p></p><pre class="language-dockerfile"><code class="lang-dockerfile">/usr/local/apache2/htdocs/
</code></pre></td></tr></tbody></table>

<mark style="background-color:yellow;">`Access`</mark>

| Public                                      | Private                                      |
| ------------------------------------------- | -------------------------------------------- |
| (select this if you want to make it public) | (select this if you want to make it private) |

<mark style="color:purple;">**Step-by-Step Guide to httpd Deployment**</mark>

1. <mark style="color:blue;">**Docker Image Selection**</mark>**:**
   * <mark style="color:orange;">Docker Image Name:</mark> <mark style="color:orange;"></mark><mark style="color:orange;">`httpd`</mark>
2. <mark style="color:orange;">**Application Details**</mark>**:**
   * Application Name: `httpd`
   * Resource Allocation: Set the desired resource allocation from 0-100%.
3. <mark style="color:orange;">**Protocol Configuration**</mark>**:**
   * Protocol: `HTTP`
   * Port: `80`
4. <mark style="color:orange;">**Installation Options**</mark>**:**
   * Choose between "Default" or "Advanced" installation.
5. <mark style="color:orange;">**Advanced Installation (Optional**</mark>**):**
   * If selecting "Advanced," you can customize the environment variables and working directory:
   * **Environment Variables:**

     Environment variables are dynamic values used by a containerized application for configuration. They are defined as key-value pairs, like `API_KEY=xyz`, and provide flexibility to adjust an app's behavior without changing its code.

     * Environment Variables: Define environment variables with keys and values (e.g., `key=value`).
   * **Working Directory:**

     The working directory is the starting point inside a container where an app's files are located. It affects relative file paths and operations. For example, if set to `/usr/src/yourAPP`, an app will reference files from there, like `/usr/src/yourAPP/data.txt`.

     * Working Directory: Set the working directory for the application (e.g., `usr/src/yourAPP`).
     * <mark style="color:red;">Here use ( use the path after   " :"  )</mark>
     *

     ````
     ```dockerfile
     ````

     ````
     /usr/local/apache2/htdocs/
     ```
     ````
6. <mark style="color:orange;">**Access Configuration**</mark>**:**
   * Choose between "Public" or "Private" access to the deployed application.
7. <mark style="color:orange;">**Installation**</mark>**:**
   * Click the "Install" button to initiate the deployment process.

By following these steps, you can effortlessly deploy an HTTPD instance with your chosen configurations. This enables you to tailor the environment to match your application's requirements and specifications. Whether opting for the default installation or delving into advanced settings, our platform ensures a seamless deployment experience while providing you the flexibility to customize according to your needs.

### <mark style="color:blue;">Visual Snapshots</mark>

<div><figure><img src="https://459768738-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtKO1h8ymGqNtYiKTJ8WZ%2Fuploads%2FmlSpMhfJDLxs8KSYEdGI%2FScreenshot%202023-09-01%20144152.png?alt=media&#x26;token=59129310-7b69-4277-8704-26087ec56276" alt=""><figcaption></figcaption></figure> <figure><img src="https://459768738-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtKO1h8ymGqNtYiKTJ8WZ%2Fuploads%2FLlJXbkkX8EQHc2Eq2H2c%2FScreenshot%202023-09-01%20144223.png?alt=media&#x26;token=7afbd6bc-6834-4895-b6d6-f2ec5c22540e" alt=""><figcaption></figcaption></figure></div>

### <mark style="color:orange;">Youtube Tutorial</mark>&#x20;

Check out our youtube video for more clarification.

### <mark style="color:blue;">FAQ</mark>

**About httpd image we used.**

This is the official httpd image.

**Can I deploy my own httpd image with modified configuration ?**

Yes, you can simply deploy any version or modified image to our platform by linking your docker hub account to our platform.

**Are my data persistent ?**

For the free user there is no persistence, and for the premium user you can different type of persistence.

### Join us

Stay informed and engaged with our project's latest developments and support on [Slack](https://app.slack.com/client/T04QS32JX6E/C04QKEWE146). Join us today to connect, collaborate, and keep the momentum going!&#x20;

<details>

<summary>Category</summary>

Kubernetes, cloud computing, DevOps, cloud services, hosting platform, container orchestration, cloud infrastructure, cloud deployment, cloud management, cloud technology, cloud solutions, httpd

</details>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://scaleinfinite.gitbook.io/docs/demo-deployment/tcp/httpd-deployment.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.