Deleted User
03/13/2023, 6:29 AMnkshah2
03/13/2023, 6:39 AMsemagraph
03/13/2023, 6:41 AMsemagraph
03/13/2023, 6:44 AMsemagraph
03/13/2023, 6:45 AMnkshah2
03/13/2023, 6:45 AMsemagraph
03/13/2023, 6:46 AMsemagraph
03/13/2023, 7:21 AMsemagraph
03/13/2023, 7:21 AMnkshah2
03/13/2023, 7:22 AMversion: '3'
services:
supertokens:
image: registry.supertokens.io/supertokens/supertokens-postgresql
depends_on:
- supertokensdatabase
ports:
- 3567:3567
environment:
POSTGRESQL_CONNECTION_URI: "postgresql://supertokens:somePassword@supertokensdatabase:5432/supertokens?schema=public"
networks:
- app_network
- supertokens_network
restart: unless-stopped
healthcheck:
test: >
bash -c 'exec 3<>/dev/tcp/127.0.0.1/3567 && echo -e "GET /hello HTTP/1.1\r\nhost: 127.0.0.1:3567\r\nConnection: close\r\n\r\n" >&3 && cat <&3 | grep "Hello"'
interval: 10s
timeout: 5s
retries: 5
supertokensdatabase:
image: 'postgres:latest'
restart: always
environment:
POSTGRES_USER: supertokens
POSTGRES_PASSWORD: somePassword
POSTGRES_DB: supertokens
ports:
- 5433:5432
networks:
- supertokens_network
volumes:
- ./volumes/postgres:/var/lib/postgresql/data
healthcheck:
test: ['CMD', 'pg_isready -U supertokens']
interval: 5s
timeout: 5s
retries: 5
networks:
app_network:
driver: bridge
supertokens_network:
driver: bridge
We renamed supertokens_database
to supertokensdatabase
(underscores are a problem here) and we changed the connection uri to postgresql://supertokens:somePassword@supertokensdatabase:5432/supertokens?schema=public
. Since the services are on the same network it needed to use the internal port and not outgoingsemagraph
03/13/2023, 7:25 AMsemagraph
03/13/2023, 7:28 AMnkshah2
03/13/2023, 7:28 AMsemagraph
03/13/2023, 7:30 AMnkshah2
03/13/2023, 7:30 AMnkshah2
03/13/2023, 7:31 AM