Automatic reverse proxying with Docker and nginx

This repository contains the docker-compose.yml file used to bring up a collection of containers that will provide automatic reverse proxying and SSL termination for other docker containers.

More details will be added here in due course. For now, the full process is described in this blog post.

Adding extra config to Nginx

Out of the box, the Nginx server will only handle HTTPS requests, with a very minimal config. The extra directory contains some additional configuration snippets which may potentially be useful.

Once you have the services running, you can copy additional config using the cp command:

docker cp file.conf autoproxy_nginx:/etc/nginx/conf.d/

The following config files are available in the extra directory:

• hsts.conf - enables HTTP Strict Transport Security for all HTTPS hosts. HSTS tells browsers that they should only ever request pages on that domain over HTTPS.
• redirect-http.conf - adds a default HTTP server that redirects all traffic to HTTPS.
• security.conf - enables some security best practices: stops Nginx reporting its version, and adds headers to help mitigate clickjacking, content type hijacking, and XSS.
• ssl.conf - adds extra SSL configuration options to disable old protocols and ciphers, enable stapling, etc. This will prevent access from older browsers and operating systems!

Hosting static content

If you’re serving static content, it’s not desirable to have lots of instances of nginx running just to handle requests from the proxy.

I recommend using GoStatic to host static content. This is a very small image that runs a very small Go binary to serve the files. You can use it in a docker-compose file like so:

---
version: '2'

services:
  www:
    image: pierrezemb/gostatic:latest
    command:
      - --forceHTTP
    labels:
      com.chameth.vhost: 'example.com'
      com.chameth.proxy: '8043'
    volumes:
      - ./www:/srv/http