Nginx proxy's docker compose template, with ACME (Let's Encrypt) support.
Read How it works documentation.
Create your own .env file based on the content of dotenv.sample file.
Docker compose should load automatically the .env file, in case you see errors regarding ${variable} not existing, then you may need to source the .env file before continuing.
Set your local environment by sourcing any of the setenv scripts, depending on your environment.
Bash and zsh shells supports the following syntax:
source ./setenv.shIf you want to source a .env.<environment> file, like .env.dev use:
source ./setenv.sh .env.dev. ./setenv.ps1If you want to source a .env.<environment> file, like .env.dev use:
. ./setenv.ps1 .env.devReview the information contained in this file regarding the creation of DH parameters file and importing existing certificates.
In order for your certificates to be stored persistently you need to use docker volume as follow.
Update the PROJECT_PATH variable in .env to reflect this project's absolute path.
Within docker-compose.services.yml you will find a set of sample applications for which nginx will auto configure its proxy, and for which SSL certificates are going to be created using Let's Encrypt though the acme_companion container.
You need to update the following variables in docker-compose.services.yml for this to work.
| Variable | Description |
|---|---|
| VIRTUAL_HOST | Comma separated list of domain names that nginx proxy will forward requests from |
| VIRTUAL_PORT | If container publishes several ports, this specify the port which nginx proxy is going to forward the requests to |
| LETSENCRYPT_HOST | Comma separated list of domain names for SSL certificate. If multiple domains are specified the first one becomes the CN (Common Name) of the certificate and the rest become the SAN (Subject Alternative Names) |
| LETSENCRYPT_EMAIL | Email address for SSL certificate registration |
Read Docker compose documentation.