mirror of
https://github.com/twentyhq/twenty.git
synced 2024-12-24 12:34: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 ``` |
||
|---|---|---|
| .. | ||
| deployment-db.yaml | ||
| deployment-redis.yaml | ||
| deployment-server.yaml | ||
| deployment-worker.yaml | ||
| ingress.yaml | ||
| pv-db.yaml | ||
| pv-docker-data.yaml | ||
| pv-server.yaml | ||
| pvc-db.yaml | ||
| pvc-docker-data.yaml | ||
| pvc-server.yaml | ||
| service-db.yaml | ||
| service-redis.yaml | ||
| service-server.yaml | ||