twenty/Makefile

postgres-on-docker:
	docker run -d \
	--name twenty_pg \
	-e PGUSER_SUPERUSER=postgres \
	-e PGPASSWORD_SUPERUSER=postgres \
	-e ALLOW_NOSSL=true \
	-v twenty_db_data:/home/postgres/pgdata \
	-p 5432:5432 \
	twentycrm/twenty-postgres-spilo:latest
	@echo "Waiting for PostgreSQL to be ready..."
	@until docker exec twenty_pg psql -U postgres -d postgres \
		-c 'SELECT pg_is_in_recovery();' 2>/dev/null | grep -q 'f'; do \
		sleep 1; \
	done
	docker exec twenty_pg psql -U postgres -d postgres \
		-c "CREATE DATABASE \"default\" WITH OWNER postgres;" \
		-c "CREATE DATABASE \"test\" WITH OWNER postgres;"

redis-on-docker:
	docker run -d --name twenty_redis -p 6379:6379 redis/redis-stack-server:latest
[Wip] Update CI CD (#2945) * Update CI and CD scripts * Fix docker docs build * Fix CD * Fix CD * Update front build and add postgres intel pg_graphql files * Fix postgres install * Fix * Update docs 2023-12-13 00:38:40 +03:00			`postgres-on-docker:`
Begin moving to postgres spilo + adding pgvector (#8309) 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 ``` 2024-11-15 11:38:30 +03:00			`docker run -d \`
			`--name twenty_pg \`
			`-e PGUSER_SUPERUSER=postgres \`
Updated website docs and /twenty-server/.env (#8801) Fix for the issue Incorrect Database Connection String in .env File #8741 --------- Co-authored-by: Félix Malfait <felix@twenty.com> 2024-11-29 16:12:09 +03:00			`-e PGPASSWORD_SUPERUSER=postgres \`
Begin moving to postgres spilo + adding pgvector (#8309) 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 ``` 2024-11-15 11:38:30 +03:00			`-e ALLOW_NOSSL=true \`
			`-v twenty_db_data:/home/postgres/pgdata \`
update makefile rules to use docker run (#7747) Fixes https://github.com/twentyhq/twenty/issues/7739 FYI @BOHEUS, thanks 2024-10-16 15:32:58 +03:00			`-p 5432:5432 \`
Begin moving to postgres spilo + adding pgvector (#8309) 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 ``` 2024-11-15 11:38:30 +03:00			`twentycrm/twenty-postgres-spilo:latest`
			`@echo "Waiting for PostgreSQL to be ready..."`
Fix Make Postgres on Docker (#8830) Fixes #8630 2024-12-02 11:58:03 +03:00			`@until docker exec twenty_pg psql -U postgres -d postgres \`
Begin moving to postgres spilo + adding pgvector (#8309) 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 ``` 2024-11-15 11:38:30 +03:00			`-c 'SELECT pg_is_in_recovery();' 2>/dev/null \| grep -q 'f'; do \`
			`sleep 1; \`
			`done`
Fix Make Postgres on Docker (#8830) Fixes #8630 2024-12-02 11:58:03 +03:00			`docker exec twenty_pg psql -U postgres -d postgres \`
Begin moving to postgres spilo + adding pgvector (#8309) 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 ``` 2024-11-15 11:38:30 +03:00			`-c "CREATE DATABASE \"default\" WITH OWNER postgres;" \`
			`-c "CREATE DATABASE \"test\" WITH OWNER postgres;"`
update makefile rules to use docker run (#7747) Fixes https://github.com/twentyhq/twenty/issues/7739 FYI @BOHEUS, thanks 2024-10-16 15:32:58 +03:00
			`redis-on-docker:`
			`docker run -d --name twenty_redis -p 6379:6379 redis/redis-stack-server:latest`