osem-fcy/docker-compose.yml.production-example
Henne Vogelsang 042d49619c Docker cleanups
- Put docker-compose.yml into version control, no need to make this an example
  file and complicate things.
- Start the docker dev-env osem on port 3000. Just as our documentation says
  and how we do it in vagrant.
- hardcode CONTAINER_USERID so you don't have to have an
  docker-compose.override.yml if your UID is 1000.
- Rename web service/container to osem for clarity in the logs
- Keep assets also in a volume in production
- warn a bit more prominently about docker-compose.override.yml
2018-09-14 23:28:26 +02:00

29 lines
582 B
Text

version: "2"
services:
database:
image: postgres
environment:
PGDATA: /var/lib/postgresql/data/pgdata
volumes:
- database:/var/lib/postgresql/data/pgdata
osem:
build: .
dockerfile: Dockerfile.production
env_file: .env.production # see dotenv.example file
depends_on:
- database
ports:
- 3000:3000
volumes:
- .:/osem
- web-data:/osem/public/system
- web-assets:/osem/public/assets
- web-logs:/osem/log
# named volumes to persist data
volumes:
database:
web-data:
web-assets:
web-logs: