certbot/docker-compose.yml

production:
  build: .
  ports:
    - "443:443"

# For development, mount git root to /opt/letsencrypt/src in order to
# make the dev workflow more vagrant-like.
development:
  build: .
  ports:
    - "443:443"
  volumes:
    - .:/opt/letsencrypt/src
    - /opt/letsencrypt/venv
sharng docker-compose.yml to add two separate container specifications: one for development (that mounts the host git root to /opt/letsencrypt/src) and one for production (that doesn't). 2015-05-19 19:53:31 -04:00			`production:`
			`build: .`
			`ports:`
			`- "443:443"`

			`# For development, mount git root to /opt/letsencrypt/src in order to`
			`# make the dev workflow more vagrant-like.`
			`development:`
Adding docker-compose file for runtime configuration 2015-03-20 19:02:43 -04:00			`build: .`
			`ports:`
			`- "443:443"`
Adding a cert path for certs generated in docker 2015-03-20 22:01:40 -04:00			`volumes:`
sharng docker-compose.yml to add two separate container specifications: one for development (that mounts the host git root to /opt/letsencrypt/src) and one for production (that doesn't). 2015-05-19 19:53:31 -04:00			`- .:/opt/letsencrypt/src`
Use a discrete path for venv in docker, rather than /opt/letsencrypt. This is useful for the docker development container, which we will want venv to persist for across runs. 2015-05-19 20:39:53 -04:00			`- /opt/letsencrypt/venv`