-
Notifications
You must be signed in to change notification settings - Fork 1
/
docker-compose.yml
61 lines (57 loc) · 1.44 KB
/
docker-compose.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
version: '3.8'
services:
backend:
container_name: backend
build:
context: ./backend
image: backend:1.0.0
restart: unless-stopped
volumes:
- ./backend/.aws:/root/.aws:ro
# to work on sandbox, point it to ~/.aws
# - ~/.aws:/root/.aws:ro
ports:
- 8000:8000
env_file:
- ./backend/.env
networks:
- main
frontend:
container_name: frontend
build:
context: ./frontend
image: frontend:1.0.0
depends_on:
- backend
restart: unless-stopped
ports:
- 3000:3000
env_file:
- ./frontend/.env
networks:
- main
localstack:
container_name: "localstack"
image: localstack/localstack
ports:
- "4566:4566"
environment:
- SERVICES=dynamodb,lambda,logs,s3
# creates a docker container everytime the lambda is invoked
- LAMBDA_EXECUTOR=docker
# necessary to invoke lambda within the docker container
- DOCKER_HOST=unix:///var/run/docker.sock
# the main entry point for all API invocations
- EDGE_PORT=4566
- AWS_DEFAULT_REGION=eu-central-1
- AWS_ACCESS_KEY_ID=testUser
- AWS_SECRET_ACCESS_KEY=testAccessKey
- DATA_DIR=/var/lib/localstack/data
volumes:
- "${PWD}/localstack:/var/lib/localstack"
# necessary to invoke lambda within the docker container
- "/var/run/docker.sock:/var/run/docker.sock"
networks:
- main
networks:
main: