nginx-proxy sets up a container running nginx and docker-gen. docker-gen generate reverse proxy configs for nginx and reloads nginx when containers they are started and stopped.

See Automated Nginx Reverse Proxy for Docker for why you might want to use this.

The template was changed to support SSL.

Now there is a VOLUME (/certs) added to Dockerfile to place the cert and key files for ssl. Naming {{host}}.crt and {{host}}.key

Usage

To run it:

$ docker run -d -p 80:80 -v /var/run/docker.sock:/tmp/docker.sock jwilder/nginx-proxy

Then start any containers you want proxied with an env var VIRTUAL_HOST=subdomain.youdomain.com

$ docker run -e VIRTUAL_HOST=foo.bar.com  ...

For SSL support add -e SSL=TRUE and place the crt and key file into the /certs folder of the nginx-proxy volume (/certs).

Provided your DNS is setup to forward foo.bar.com to the a host running nginx-proxy, the request will be routed to a container with the VIRTUAL_HOST env var set.

Multiple Ports

If your container exposes multiple ports, nginx-proxy will default to the service running on port 80. If you need to specify a different port, you can set a VIRTUAL_PORT env var to select a different one. If your container only exposes one port and it has a VIRTUAL_HOST env var set, that port will be selected. This is not working for ssl for now.

Multiple Hosts

If you need to support multipe virtual hosts for a container, you can separate each enty with commas. For example, foo.bar.com,baz.bar.com,bar.com and each host will be setup the same.