mirror of
https://github.com/twentyhq/twenty.git
synced 2024-12-23 12:02:10 +03:00
736635a94b
We will remove the `twenty-postgres` image that was used for local development and only use `twenty-postgres-pilo` (which we use in prod), bringing the development environment closer to prod and avoiding having to maintain 2 images. Instead of provisioning the super user after the db initialization, we directly rely on the superuser provided by Spilo for simplicity. We also introduce a change that tries to create the right database (`default` or `test`) based on the context. How to test: ``` docker build -t twentycrm/twenty-postgres-spilo:latest -f ./packages/twenty-docker/twenty-postgres-spilo/Dockerfile . docker images --no-trunc | grep twenty-postgres-spilo postgres-on-docker: docker run \ --name twenty_pg \ -e PGUSER_SUPERUSER=twenty \ -e PGPASSWORD_SUPERUSER=twenty \ -e ALLOW_NOSSL=true \ -v twenty_db_data:/home/postgres/pgdata \ -p 5432:5432 \ REPLACE_WITH_IMAGE_ID ```
21 lines
401 B
Plaintext
21 lines
401 B
Plaintext
TAG=latest
|
|
|
|
#PGUSER_SUPERUSER=postgres
|
|
#PGPASSWORD_SUPERUSER=replace_me_with_a_strong_password
|
|
|
|
PG_DATABASE_HOST=db:5432
|
|
REDIS_URL=redis://redis:6379
|
|
|
|
SERVER_URL=http://localhost:3000
|
|
|
|
# Use openssl rand -base64 32 for each secret
|
|
# APP_SECRET=replace_me_with_a_random_string
|
|
|
|
SIGN_IN_PREFILLED=true
|
|
|
|
STORAGE_TYPE=local
|
|
|
|
# STORAGE_S3_REGION=eu-west3
|
|
# STORAGE_S3_NAME=my-bucket
|
|
# STORAGE_S3_ENDPOINT=
|