This image is based on the official 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: watcherd and 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, reverse proxy (with or without websocket support)..
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.
|Invalid backend string||Backend Suggestion||Invalid Alias||Verified|
|Web Server Project||Reference Implementation|
|Streamlined Webserver images||The Devilbox|
Apache 2.2 | Apache 2.4 | Nginx stable | Nginx mainline
🐋 Available Docker tags
docker pull devilbox/nginx-mainline
The following Docker image tags are rolling releases and are built and updated every night.
|Docker Tag||Git Ref||Available Architectures|
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.
|Docker Tag||Git Ref||Available Architectures|
<tag>refers to the chosen git tag from this repository.
⚠Warning: The latest available git tag is also build every night and considered a rolling tag.
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. It distinguishes between HTTP backends (
https://) and Websocket backends (
wss://) automatically and configures accordingly.
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
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
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 runcommand 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.
The provided Docker images offer the following internal paths to be mounted to your local file system.
🛈 For details see Documentation: Volumes
|Data dir||Config dir|
🖧 Exposed Ports
When you plan on using
443 you must enable SSL via environment variables, otherwise nothing will be listening on that port.
|80||HTTP listening Port|
|443||HTTPS listening Port|
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
The following diagram shows the basic architecture of this docker image.
🛈 For details see Documentation: Architecture
# 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.
In case you seek help, go and visit the community pages.
I try to keep up with literally over 100 projects besides a full-time job.
If my work is making your life easier, consider contributing.
Contrib: PyPI: cytopia · Terraform: cytopia · Ansible: cytopia
Copyright (c) 2016 cytopia