devilbox/nginx-mainline

Nginx mainline

https://github.com/devilbox/docker-nginx-mainline/workflows/lint/badge.svg](https://github.com/devilbox/docker-nginx-mainline/actions?query=workflow%3Alint) https://github.com/devilbox/docker-nginx-mainline/workflows/build/badge.svg](https://github.com/devilbox/docker-nginx-mainline/actions?query=workflow%3Abuild) https://github.com/devilbox/docker-nginx-mainline/workflows/nightly/badge.svg](https://github.com/devilbox/docker-nginx-mainline/actions?query=workflow%3Anightly) ![License]([***]

![]([] ![Discourse]([***]

Available Architectures: amd64, arm64, 386, arm/v7, arm/v6

This image is based on the official https://hub.docker.com/_/nginx Docker image and extends it with the ability to have virtual hosts created automatically, as well as adding SSL certificates when creating new directories. For that to work, it integrates two tools that will take care about the whole process: https://github.com/devilbox/watcherd and https://github.com/devilbox/vhost-gen.

From a users perspective, you mount your local project directory into the container under /shared/httpd. Any directory then created in your local project directory wil spawn a new virtual host by the same name. Each virtual host optionally supports a generic or custom backend configuration (static files, PHP-FPM or reverse proxy).

HTTP/2 is enabled by default for all SSL connections.

For convenience the entrypoint script during docker run provides a pretty decent validation and documentation about wrong user input and suggests steps to fix it.

🐱 GitHub: https://github.com/devilbox/docker-nginx-mainline

https://github.com/devilbox/docker-apache-2.2 | https://github.com/devilbox/docker-apache-2.4 | https://github.com/devilbox/docker-nginx-stable | Nginx mainline

🐋 Available Docker tags

https://github.com/devilbox/docker-nginx-mainline/blob/master/Dockerfiles/Dockerfile.latest https://github.com/devilbox/docker-nginx-mainline/blob/master/Dockerfiles/Dockerfile.debian https://github.com/devilbox/docker-nginx-mainline/blob/master/Dockerfiles/Dockerfile.alpine

bash
docker pull devilbox/nginx-mainline

Rolling releases

The following Docker image tags are rolling releases and are built and updated every night.

https://github.com/devilbox/docker-nginx-mainline/workflows/nightly/badge.svg](https://github.com/devilbox/docker-nginx-mainline/actions?query=workflow%3Anightly)

Point in time releases

The following Docker image tags are built once and can be used for reproducible builds. Its version never changes so you will have to update tags in your pipelines from time to time in order to stay up-to-date.

https://github.com/devilbox/docker-nginx-mainline/workflows/build/badge.svg](https://github.com/devilbox/docker-nginx-mainline/actions?query=workflow%3Abuild)

🛈 Where <tag> refers to the chosen git tag from this repository.
⚠ Warning: The latest available git tag is also build every night and ***ed a rolling tag.

✰ Features

This repository uses official httpd Docker images and adds a lot of features, logic and autmomation op top. This allows you to feature-toggle certain functionality simply by setting environment variables.

Below is a brief overview about most outstanding features, but I would still advice you to read up on available environment variables, as well as the architecture to get the whole picture.

🛈 For details see Documentation: Features

Automated mass virtual hosts

• Virtual hosts are created automatically, simply by creating a new project directory (inside or outside of the container). This allows you to quickly create new projects and work on them in your IDE without the hassle of configuring the web server.

Automated PHP-FPM setup

• PHP is not included in the provided images, but you can enable a remote backend and link it to a PHP-FPM image. This allows you to easily switch PHP versions and choose one which is currently required.

Automated Reverse Proxy setup

• In reverse proxy mode, you can choose any http or https backend of your likings. This way you can proxy NodeJS, Python, etc. and use the webserver to add SSL in front.

Automated SSL certificate generation

• SSL certificates are generated automatically for each virtual host if you choose to enable it

Trusted HTTPS in all vhosts

• Virtual host SSL certificates are signed by an internal Certificate Authority (or one you provide to the image). That makes it possible to set the CA to trusted and all generated vhosts will automatically have trusted SSL.

Customization per virtual host

• Each virtual host can individually be fully customized via https://github.com/devilbox/vhost-gen templates.

Local file system permission sync

• File system permission/ownership of files/dirs inside the running container can be synced with the permission on your host system. This is accomplished by specifying a user- and group-id to the docker run command.

Tested with common Frameworks

• Wordpress, Drupal, Laravel, CakePHP, PhalconPHP, Magento, Shopware, Typo3, Yii, Zend and many others.

∑ Environment Variables

The provided Docker images add a lot of injectables in order to customize it to your needs. See the table below for a brief overview.

🛈 For details see Documentation: Environment variables

If you don't feel like reading the documentation, simply try out your docker run command and add any environment variables specified below. The validation will tell you what you might have done wrong, how to fix it and what the meaning is.

📂 Volumes

The provided Docker images offer the following internal paths to be mounted to your local file system.

🛈 For details see Documentation: Volumes

🖧 Exposed Ports

When you plan on using 443 you must enable SSL via environment variables, otherwise nothing will be listening on that port.

💡 Examples

The documentation provides many copy/paste examples about common use-cases including dummy projects.

The given examples distinguish between two different kinds of setup: The default vhost, which only allows to serve a single project and the mass vhost setup, which allows unlimited vhosts that are created automtically. Both types offer the same set of features and are configured in a similar way, so If you find an example in one kind it is easily applyable to the other kind as well.

🛈 For details see Documentation: Examples
🛈 For details see Docker Compose: Examples

Docker

Docker Compose

👷 Architecture

The following diagram shows the basic architecture of this docker image.

🛈 For details see Documentation: Architecture

bash
       # mass-vhost                                     # main-vhost only
       docker-entrypoint.sh                             docker-entrypoint.sh
                |                                                |
                ↓                                                ↓
           supervisord (pid 1)                                 httpd (pid 1)
          /     |
         /      |
       ↙        ↓
  start       start
  httpd      watcherd
            /    |    \
           /     |     \
          ↓      ↓      ↘
        sgn     rm      create-vhost.sh
       httpd   vhost     |           |
                         |           |
                         ↓           ↓
                      cert-gen    vhost-gen ⭢ generate vhost

🖤 Sister Projects

Show some love for the following sister projects.

👫 Community

In case you seek help, go and visit the community pages.

</a>

</a>

</a>

🧘 Maintainer

https://github.com/cytopia

I try to keep up with literally over 100 projects besides a full-time job. If my work is making your life easier, *** contributing. 🖤

• https://github.com/***/cytopia
• Patreon
• Open Collective

Findme: 🐱 https://github.com/cytopia / https://github.com/devilbox | 🐋 https://hub.docker.com/r/cytopia/ / https://hub.docker.com/r/devilbox/ | 🐦 everythingcli / devilbox | 📖 everythingcli.org

Contrib: PyPI: cytopia · Terraform: cytopia · Ansible: cytopia

🗎 License

MIT License

Copyright (c) 2016 https://github.com/cytopia