zombi/nginx-proxy
Archived
11
0
Fork 0
Code Issues Pull requests Releases Activity
No description
This repository has been archived on 2020-08-01. You can view files and clone it, but cannot push or open issues or pull requests.
14 commits 1 branch 4 tags 229 KiB
Shell 96.5%
Dockerfile 2.9%
Makefile 0.6%
Find a file
Jason Wilder 4f3d690cd3 Stream logs to stdout/err 
Nginx and docker-gen logs can now be seen via docker logs.
2014-06-03 16:30:05 -06:00
Dockerfile Stream logs to stdout/err 2014-06-03 16:30:05 -06:00
nginx.tmpl Stream logs to stdout/err 2014-06-03 16:30:05 -06:00
Procfile Stream logs to stdout/err 2014-06-03 16:30:05 -06:00
README.md Remove embedded Dockerfile contents 2014-05-20 09:40:38 -06:00

README.md

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.

Usage

To run it:

$ docker run -d -p 80:80 -v /var/run/docker.sock:/tmp/docker.sock -t 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 -t ...

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.