-
Notifications
You must be signed in to change notification settings - Fork 0
/
docker-compose-prod.yml
112 lines (101 loc) · 3.85 KB
/
docker-compose-prod.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
# Production environment docker compose file
# Version of docker compose to use
version: '3.9'
# services we want to run
services:
app:
# NOTE: opting for 'always' will always restart service even if you try to stop it
restart: unless-stopped
# NOTE: If hosting images on docker hub, ECR or similar,
# CONTD: you can use the repository URI making it easy to push and pull images.
# CONTD: (ECR example) image: <myactid>.dkr.ecr.us-east-1.amazonaws.com/<myrepo>:app
# CONTD: then you can run docker compose -f docker-compose-prod.yml push or pull
# image name and a tag name
image: app:app
# Any name that can further help ID this container
container_name: django_container
build: .
expose:
- 9000
links:
- postgres:postgres
- redis:redis
volumes:
# persist static files beyond the life of the container
- static_volume:/vol/web/static
- media_volume:/vol/web/media
env_file:
# env. file containing variables to use within this service
- ./.env
depends_on:
- postgres
nginx:
# NOTE: opting for 'always' will always restart service even if you try to stop it
restart: unless-stopped
# NOTE: If hosting images on docker hub, ECR or similar,
# CONTD: you can use the repository URI making it easy to push and pull images.
# CONTD: (ECR example) image: <myactid>.dkr.ecr.us-east-1.amazonaws.com/<myrepo>:nginx
# CONTD: then you can run docker compose -f docker-compose-prod.yml push or pull
# image name and a tag name
image: nginx:nginx
# Any name that can further help ID this container
container_name: nginx_container
build: ./docker-services/nginx/
ports:
- "80:8000"
- 443:443
volumes:
- static_volume:/vol/static
- media_volume:/vol/media
- /var/www/html:/var/www/html
- /etc/letsencrypt:/etc/letsencrypt
- /var/lib/letsencrypt:/var/lib/letsencrypt
links:
- app:app
depends_on:
- app
postgres:
# NOTE: opting for 'always' will always restart service even if you try to stop it
restart: unless-stopped
# NOTE: If hosting images on docker hub, ECR or similar,
# CONTD: you can use the repository URI making it easy to push and pull images.
# CONTD: (ECR example) image: <myactid>.dkr.ecr.us-east-1.amazonaws.com/<myrepo>:postgres
# CONTD: then you can run docker compose -f docker-compose-prod.yml push or pull
# image name and a tag name
image: postgres:postgres
# Any name that can further help ID this container
container_name: postgres_container
build: ./docker-services/postgres/
ports:
- "5432:5432"
volumes:
# NOTE: Don't manage db in the container. Its easy to wipe data unknowingly.
# CONTD: eg. you might need to run docker compose -f docker-compose-prod.yml down -v
# CONTD: an action that will wipe all services volumes incl. db data.
# CONTD: Use RDS or similar
# persist db data beyond the life of the container
- pgdata:/var/lib/postgresql/data/
environment:
- POSTGRES_DB=${DB_NAME}
- POSTGRES_PASSWORD=${DB_PASSWORD}
- POSTGRES_USER=${DB_USER}
redis:
# NOTE: opting for 'always' will always restart service even if you try to stop it
restart: unless-stopped
# NOTE: If hosting images on docker hub, ECR or similar,
# CONTD: you can use the repository URI making it easy to push and pull images.
# CONTD: (ECR example) image: <myactid>.dkr.ecr.us-east-1.amazonaws.com/<myrepo>:redis
# CONTD: then you can run docker compose -f docker-compose-prod.yml push or pull
# image name and a tag name
image: redis:redis
build: ./docker-services/redis/
container_name: homey_redis_container
ports:
- "6379:6379"
volumes:
- redisdata:/data
volumes:
static_volume:
media_volume:
pgdata:
redisdata: