Coolify installation

[boringcommerce]

Hi, is there a way to install this on coolify, using one-click or something?

[FelixMalfait]

I don't think anyone has built a Coolify deployment setup yet. The install still evolves quite frequently so the 1-click button we tried to build tends to break. It'll get more stable in a few months!

[Abz2604]

I actually tried the same and getting some reference errors in the docker-compose file. Would be amazing if we could get a little hint as to what we can alter to make it work! :)

Currently facing:

[2024-May-02 09:50:37.638014] time="2024-05-02T09:50:37Z" level=warning msg="The "TAG" variable is not set. Defaulting to a blank string."
time="2024-05-02T09:50:37Z" level=warning msg="The "TAG" variable is not set. Defaulting to a blank string."
time="2024-05-02T09:50:37Z" level=warning msg="The "PG_DATABASE_HOST" variable is not set. Defaulting to a blank string."
time="2024-05-02T09:50:37Z" level=warning msg="/artifacts/vkco0co/packages/twenty-docker/docker-compose.yml: version is obsolete"
unable to get image 'twentycrm/twenty:': Error response from daemon: invalid reference format

[janbiasi]

There is a service preset for deploying twenty on coolify 😄

[FelixMalfait]

Oh nice I didn't know! Thanks for sharing

[ashayramolia]

its been disabled for now, the compose file no longer works. issues citing how twenty's internal docker configuration has changed.

[gvzq]

I keep getting an error. It's trying to hit https://crm.domain.com//graphql using this preset:

{statusCode: 404, message: "Cannot POST //graphql", error: "Not Found"}

Solution: I had to "edit compose file" and replace the server_url and front_base_url:

      - 'SERVER_URL=https://crm.domain.com'
      - 'FRONT_BASE_URL=https://crm.domain.com'
      

[janbiasi]

Yep, that's indeed an issue in coolify itself, the FQDN should not include the trailing slash. The workaround is completely fine.
There's already an open discussion for this topic on coolify to get this fixed.

[Abz2604]

Even I'm facing this 404 error. And this workaround of editing the compose file doesnt seem to work in my case.

[janbiasi]

@Abz2604 would you mind posting your docker compose for further assistance?

[tanyudii]

Even I'm facing this 404 error. And this workaround of editing the compose file doesnt seem to work in my case.

trying to add at twenty services. its work for me

ports:
 - '3000'

[nooruddin-rahmani]

Hello everyone hope you're doing great.
I am new to deploying apps and do not know the basics well.
I tried to deploy Twenty in Coolify from GitHub repo. After deploying, When I want to access Twenty, I get Bad Gateway any idea how it happens.
However when I want to deploy the pre-built one that Coolify provides it runs fine.

[FelixMalfait]

Hey, maybe that's because we recently added Redis as a depedency and the Coolify config hasn't been updated? I've never used Coolify so I'm not really familiar with how it works

[nooruddin-rahmani]

Well as I checked the Coolify itself provides a pre-built option to deploy Twenty CRM but the thing is I wanna have some changes on the CRM itself, if possible and I am comfortable working on a github repo. So I think if I can deploy Twenty via Github repo I can change things easily.

[FelixMalfait]

Sure you can, our codebase is not very easy to grasp. We're working on making extensibility much easier next year!

[janbiasi]

Hey @nooruddin-rahmani

I got twenty up and running via coolify myself. You can find my docker-compose configuration below.
One thing to note is that you manually need to adjust the FQDN to not include a trailing slash and set the SERVER_URL to your configured public domain. The current preset in the repository isn't quite up to date, I'll file a PR soon to align it to the current requirements.

services:
  twenty:
    image: 'twentycrm/twenty:v0.30'
    environment:
      - SERVICE_FQDN_TRIGGER_3000
      - SERVER_URL=$SERVER_URL
      - FRONT_BASE_URL=$SERVER_URL
      - ENABLE_DB_MIGRATIONS=true
      - 'CACHE_STORAGE_TYPE=${CACHE_STORAGE_TYPE:-redis}'
      - REDIS_HOST=redis
      - REDIS_PORT=6379
      - 'API_RATE_LIMITING_TTL=${API_RATE_LIMITING_TTL:-100}'
      - 'API_RATE_LIMITING_LIMIT=${API_RATE_LIMITING_LIMIT:-100}'
      - ACCESS_TOKEN_SECRET=$SERVICE_BASE64_32_ACCESS
      - LOGIN_TOKEN_SECRET=$SERVICE_BASE64_32_LOGIN
      - REFRESH_TOKEN_SECRET=$SERVICE_BASE64_32_REFRESH
      - FILE_TOKEN_SECRET=$SERVICE_BASE64_32_FILE
      - POSTGRES_ADMIN_PASSWORD=$SERVICE_PASSWORD_POSTGRES
      - 'PG_DATABASE_URL=postgres://postgres:$SERVICE_PASSWORD_POSTGRES@postgres:5432/default'
      - 'IS_SIGN_UP_DISABLED=${IS_SIGN_UP_DISABLED:-false}'
      - 'PASSWORD_RESET_TOKEN_EXPIRES_IN=${PASSWORD_RESET_TOKEN_EXPIRES_IN:-5m}'
      - WORKSPACE_INACTIVE_DAYS_BEFORE_NOTIFICATION=$WORKSPACE_INACTIVE_DAYS_BEFORE_NOTIFICATION
      - WORKSPACE_INACTIVE_DAYS_BEFORE_DELETION=$WORKSPACE_INACTIVE_DAYS_BEFORE_DELETION
      - 'STORAGE_TYPE=${STORAGE_TYPE:-local}'
      - STORAGE_S3_REGION=$STORAGE_S3_REGION
      - STORAGE_S3_NAME=$STORAGE_S3_NAME
      - STORAGE_S3_ENDPOINT=$STORAGE_S3_ENDPOINT
      - STORAGE_S3_ACCESS_KEY_ID=$STORAGE_S3_ACCESS_KEY_ID
      - STORAGE_S3_SECRET_ACCESS_KEY=$STORAGE_S3_SECRET_ACCESS_KEY
      - MESSAGE_QUEUE_TYPE=$MESSAGE_QUEUE_TYPE
      - EMAIL_FROM_ADDRESS=$EMAIL_FROM_ADDRESS
      - EMAIL_FROM_NAME=$EMAIL_FROM_NAME
      - EMAIL_SYSTEM_ADDRESS=$EMAIL_SYSTEM_ADDRESS
      - 'EMAIL_DRIVER=${EMAIL_DRIVER:-logger}'
      - EMAIL_SMTP_HOST=$EMAIL_SMTP_HOST
      - EMAIL_SMTP_PORT=$EMAIL_SMTP_PORT
      - EMAIL_SMTP_USER=$EMAIL_SMTP_USER
      - EMAIL_SMTP_PASSWORD=$EMAIL_SMTP_PASSWORD
      - SIGN_IN_PREFILLED=false
      - 'DEBUG_MODE=${DEBUG_MODE:-false}'
      - 'TELEMETRY_ENABLED=${TELEMETRY_ENABLED:-false}'
    depends_on:
      postgres:
        condition: service_healthy
      redis:
        condition: service_healthy
    healthcheck:
      test: 'curl --fail -6 "http://[::1]:3000/healthz"'
      interval: 5s
      timeout: 10s
      retries: 25
  worker:
    image: 'twentycrm/twenty:v0.30'
    command:
      - yarn
      - 'worker:prod'
    environment:
      - SERVER_URL=$SERVER_URL
      - 'FRONT_BASE_URL=${FRONT_BASE_URL:-$SERVER_URL}'
      - 'PG_DATABASE_URL=postgres://postgres:$SERVICE_PASSWORD_POSTGRES@postgres:5432/default'
      - 'MESSAGE_QUEUE_TYPE=${MESSAGE_QUEUE_TYPE:-pg-boss}'
      - REDIS_HOST=redis
      - REDIS_PORT=6379
      - ENABLE_DB_MIGRATIONS=false
      - STORAGE_TYPE=$STORAGE_TYPE
      - STORAGE_S3_REGION=$STORAGE_S3_REGION
      - STORAGE_S3_NAME=$STORAGE_S3_NAME
      - STORAGE_S3_ENDPOINT=$STORAGE_S3_ENDPOINT
      - STORAGE_S3_ACCESS_KEY_ID=$STORAGE_S3_ACCESS_KEY_ID
      - STORAGE_S3_SECRET_ACCESS_KEY=$STORAGE_S3_SECRET_ACCESS_KEY
      - ACCESS_TOKEN_SECRET=$SERVICE_BASE64_32_ACCESS
      - LOGIN_TOKEN_SECRET=$SERVICE_BASE64_32_LOGIN
      - REFRESH_TOKEN_SECRET=$SERVICE_BASE64_32_REFRESH
      - FILE_TOKEN_SECRET=$SERVICE_BASE64_32_FILE
    depends_on:
      redis:
        condition: service_healthy
      twenty:
        condition: service_healthy
    restart: always
  postgres:
    image: 'twentycrm/twenty-postgres:latest'
    environment:
      - POSTGRES_USER=postgres
      - POSTGRES_PASSWORD=$SERVICE_PASSWORD_POSTGRES
      - POSTGRES_DB=default
    volumes:
      - 'pg-data:/bitnami/postgresql'
    healthcheck:
      test:
        - CMD-SHELL
        - 'pg_isready -U $${POSTGRES_USER} -d $${POSTGRES_DB}'
      interval: 5s
      timeout: 20s
      retries: 10
  redis:
    image: 'redis:latest'
    volumes:
      - 'redis-data:/data'
    healthcheck:
      test:
        - CMD
        - redis-cli
        - ping
      interval: 5s
      timeout: 20s
      retries: 10

Note: you may want to adjust the image version based on your own needs.

[FelixMalfait]

Hey @janbiasi thanks for supporting the community with this! I didn't understand the issue with the trailing slash but if there's any way to fix the issue on our side please feel free to raise a PR! Thanks!

[olivermontes]

im try upgrade from new docker-compose Twenty https://github.com/twentyhq/twenty/blob/main/packages/twenty-docker/docker-compose.yml

• now problem is bash: line 40: unexpected EOF while looking for matching `"'

My try to fixed

version: "3.9"
name: twenty

services:
  change-vol-ownership:
    image: ubuntu
    user: root
    volumes:
      - server-local-data:/tmp/server-local-data
      - docker-data:/tmp/docker-data
    command: >
      bash -c "
      chown -R 1000:1000 /tmp/server-local-data
      && chown -R 1000:1000 /tmp/docker-data"
    pull_policy: if_not_present

  server:
    image: twentycrm/twenty:${TAG}
    volumes:
      # Cambiado para usar una ruta fija en lugar de variable
      - server-local-data:/app/packages/twenty-server/.local-storage
      - docker-data:/app/docker-data
    ports:
      - "3000:3000"
    environment:
      PORT: 3000
      PG_DATABASE_URL: postgres://${PGUSER_SUPERUSER:-postgres}:${PGPASSWORD_SUPERUSER:-twenty}@${PG_DATABASE_HOST:-db:5432}/default
      SERVER_URL: ${SERVER_URL}
      FRONT_BASE_URL: ${FRONT_BASE_URL:-$SERVER_URL}
      REDIS_URL: ${REDIS_URL:-redis://redis:6379}
      ENABLE_DB_MIGRATIONS: "true"
      SIGN_IN_PREFILLED: ${SIGN_IN_PREFILLED}
      STORAGE_TYPE: ${STORAGE_TYPE}
      STORAGE_S3_REGION: ${STORAGE_S3_REGION}
      STORAGE_S3_NAME: ${STORAGE_S3_NAME}
      STORAGE_S3_ENDPOINT: ${STORAGE_S3_ENDPOINT}
      APP_SECRET: ${APP_SECRET}
    pull_policy: if_not_present
    depends_on:
      change-vol-ownership:
        condition: service_completed_successfully
      db:
        condition: service_healthy
    healthcheck:
      test: curl --fail http://localhost:3000/healthz
      interval: 5s
      timeout: 5s
      retries: 10
    restart: always

  worker:
    image: twentycrm/twenty:${TAG}
    command: ["yarn", "worker:prod"]
    environment:
      PG_DATABASE_URL: postgres://${PGUSER_SUPERUSER:-postgres}:${PGPASSWORD_SUPERUSER:-twenty}@${PG_DATABASE_HOST:-db:5432}/default
      SERVER_URL: ${SERVER_URL}
      FRONT_BASE_URL: ${FRONT_BASE_URL:-$SERVER_URL}
      REDIS_URL: ${REDIS_URL:-redis://redis:6379}
      ENABLE_DB_MIGRATIONS: "false"
      STORAGE_TYPE: ${STORAGE_TYPE}
      STORAGE_S3_REGION: ${STORAGE_S3_REGION}
      STORAGE_S3_NAME: ${STORAGE_S3_NAME}
      STORAGE_S3_ENDPOINT: ${STORAGE_S3_ENDPOINT}
      APP_SECRET: ${APP_SECRET}
    pull_policy: if_not_present
    depends_on:
      db:
        condition: service_healthy
      server:
        condition: service_healthy
    restart: always

  db:
    image: twentycrm/twenty-postgres-spilo:${TAG}
    volumes:
      - db-data:/home/postgres/pgdata
    environment:
      PGUSER_SUPERUSER: ${PGUSER_SUPERUSER:-postgres}
      PGPASSWORD_SUPERUSER: ${PGPASSWORD_SUPERUSER:-twenty}
      ALLOW_NOSSL: "true"
      SPILO_PROVIDER: "local"
    pull_policy: if_not_present
    healthcheck:
      test: pg_isready -U ${PGUSER_SUPERUSER:-postgres} -h localhost -d postgres
      interval: 5s
      timeout: 5s
      retries: 10
    restart: always

  redis:
    image: redis
    pull_policy: if_not_present
    restart: always

volumes:
  docker-data:
  db-data:
  server-local-data:

[Nirator78]

Same error here

[Termina94]

I have a docker compose that solves the pgvector requirement issues:

then sh into twenty service and mkdir /app/docker-data/

Everything will run up to '[NestApplication] Nest application successfully started'

However, I cannot access the gui from the domain ($SERVICE_FQDN_TWENTY)

Getting hit with the 'no available server' on page load

services:
  twenty:
    image: 'twentycrm/twenty:latest'
    environment:
      - SERVICE_FQDN_TWENTY_3000
      - SERVER_URL=$SERVICE_FQDN_TWENTY
      - FRONT_BASE_URL=$SERVICE_FQDN_TWENTY
      - ENABLE_DB_MIGRATIONS=true
      - 'CACHE_STORAGE_TYPE=${CACHE_STORAGE_TYPE:-redis}'
      - 'REDIS_URL=redis://redis:6379'
      - 'API_RATE_LIMITING_TTL=${API_RATE_LIMITING_TTL:-100}'
      - 'API_RATE_LIMITING_LIMIT=${API_RATE_LIMITING_LIMIT:-100}'
      - APP_SECRET=$SERVICE_BASE64_32_SECRET
      - POSTGRES_ADMIN_PASSWORD=$SERVICE_PASSWORD_POSTGRES
      - 'PG_DATABASE_URL=postgres://postgres:$SERVICE_PASSWORD_POSTGRES@postgres:5432/default'
      - 'IS_SIGN_UP_DISABLED=${IS_SIGN_UP_DISABLED:-false}'
      - 'PASSWORD_RESET_TOKEN_EXPIRES_IN=${PASSWORD_RESET_TOKEN_EXPIRES_IN:-5m}'
      - 'STORAGE_TYPE=${STORAGE_TYPE:-local}'
      - STORAGE_S3_REGION=$STORAGE_S3_REGION
      - STORAGE_S3_NAME=$STORAGE_S3_NAME
      - STORAGE_S3_ENDPOINT=$STORAGE_S3_ENDPOINT
      - STORAGE_S3_ACCESS_KEY_ID=$STORAGE_S3_ACCESS_KEY_ID
      - STORAGE_S3_SECRET_ACCESS_KEY=$STORAGE_S3_SECRET_ACCESS_KEY
      - 'MESSAGE_QUEUE_TYPE=${MESSAGE_QUEUE_TYPE:-pg-boss}'
      - EMAIL_FROM_ADDRESS=$EMAIL_FROM_ADDRESS
      - EMAIL_FROM_NAME=$EMAIL_FROM_NAME
      - EMAIL_SYSTEM_ADDRESS=$EMAIL_SYSTEM_ADDRESS
      - 'EMAIL_DRIVER=${EMAIL_DRIVER:-logger}'
      - EMAIL_SMTP_HOST=$EMAIL_SMTP_HOST
      - EMAIL_SMTP_PORT=$EMAIL_SMTP_PORT
      - EMAIL_SMTP_USER=$EMAIL_SMTP_USER
      - EMAIL_SMTP_PASSWORD=$EMAIL_SMTP_PASSWORD
      - SIGN_IN_PREFILLED=false
      - 'DEBUG_MODE=${DEBUG_MODE:-false}'
      - 'TELEMETRY_ENABLED=${TELEMETRY_ENABLED:-false}'
    depends_on:
      postgres:
        condition: service_healthy
    healthcheck:
      test:
        - CMD
        - curl
        - '-f'
        - 'http://127.0.0.1:3000/healthz'
      interval: 2s
      timeout: 10s
      retries: 15
  postgres:
    image: ramsrib/pgvector
    environment:
      - POSTGRES_USER=postgres
      - POSTGRES_PASSWORD=$SERVICE_PASSWORD_POSTGRES
      - POSTGRES_DB=default
    volumes:
      - 'pg-data:/bitnami/postgresql'
    healthcheck:
      test:
        - CMD-SHELL
        - 'pg_isready -U $${POSTGRES_USER} -d $${POSTGRES_DB}'
      interval: 5s
      timeout: 20s
      retries: 10
  redis:
    image: 'redis:latest'
    volumes:
      - 'redis-data:/data'
    healthcheck:
      test:
        - CMD
        - redis-cli
        - ping
      interval: 5s
      timeout: 20s
      retries: 10

[Nirator78]

@Termina94 For me it's just looping on the migration execution not Nestjs launch.

[Termina94]

Mine was erroring about a folder not existing, if you terminal into twenty service and ‘mkdir /app/docker-data/‘ it should move ahead to nestjs launch

[Nirator78]

Thank you it's work now ;) Next time i will read your post complety

[mydalat]

Hey guys, if we run on Coolify, how can we back up and restore safely? Is anyone using Coolify to host Twenty? What do we need to do?

[ashayramolia]

i am in the same boat as you for now, havent been able to even deploy it correctly.
issues citing broken compose or docker file is all i see here or on coolify

[Rabbittoly]

This version worked for me. The application loaded successfully.

services:
  twenty:
    image: 'twentycrm/twenty:v0.30.0'
    ports:
      - "3000:3000"
    environment:
      - SERVICE_FQDN_TRIGGER_3000
      - SERVER_URL=$SERVER_URL
      - FRONT_BASE_URL=$SERVER_URL
      - ENABLE_DB_MIGRATIONS=true
      - CORS_ORIGIN=*
      - 'CACHE_STORAGE_TYPE=${CACHE_STORAGE_TYPE:-redis}'
      - REDIS_HOST=redis
      - REDIS_PORT=6379
      - 'API_RATE_LIMITING_TTL=${API_RATE_LIMITING_TTL:-100}'
      - 'API_RATE_LIMITING_LIMIT=${API_RATE_LIMITING_LIMIT:-100}'
      - ACCESS_TOKEN_SECRET=$SERVICE_BASE64_32_ACCESS
      - LOGIN_TOKEN_SECRET=$SERVICE_BASE64_32_LOGIN
      - REFRESH_TOKEN_SECRET=$SERVICE_BASE64_32_REFRESH
      - FILE_TOKEN_SECRET=$SERVICE_BASE64_32_FILE
      - POSTGRES_ADMIN_PASSWORD=$SERVICE_PASSWORD_POSTGRES
      - 'PG_DATABASE_URL=postgres://postgres:$SERVICE_PASSWORD_POSTGRES@postgres:5432/default'
      - 'IS_SIGN_UP_DISABLED=${IS_SIGN_UP_DISABLED:-false}'
      - 'PASSWORD_RESET_TOKEN_EXPIRES_IN=${PASSWORD_RESET_TOKEN_EXPIRES_IN:-5m}'
      - WORKSPACE_INACTIVE_DAYS_BEFORE_NOTIFICATION=$WORKSPACE_INACTIVE_DAYS_BEFORE_NOTIFICATION
      - WORKSPACE_INACTIVE_DAYS_BEFORE_DELETION=$WORKSPACE_INACTIVE_DAYS_BEFORE_DELETION
      - 'STORAGE_TYPE=${STORAGE_TYPE:-local}'
      - STORAGE_S3_REGION=$STORAGE_S3_REGION
      - STORAGE_S3_NAME=$STORAGE_S3_NAME
      - STORAGE_S3_ENDPOINT=$STORAGE_S3_ENDPOINT
      - STORAGE_S3_ACCESS_KEY_ID=$STORAGE_S3_ACCESS_KEY_ID
      - STORAGE_S3_SECRET_ACCESS_KEY=$STORAGE_S3_SECRET_ACCESS_KEY
      - 'MESSAGE_QUEUE_TYPE=${MESSAGE_QUEUE_TYPE:-pg-boss}'
      - EMAIL_FROM_ADDRESS=$EMAIL_FROM_ADDRESS
      - EMAIL_FROM_NAME=$EMAIL_FROM_NAME
      - EMAIL_SYSTEM_ADDRESS=$EMAIL_SYSTEM_ADDRESS
      - 'EMAIL_DRIVER=${EMAIL_DRIVER:-logger}'
      - EMAIL_SMTP_HOST=$EMAIL_SMTP_HOST
      - EMAIL_SMTP_PORT=$EMAIL_SMTP_PORT
      - EMAIL_SMTP_USER=$EMAIL_SMTP_USER
      - EMAIL_SMTP_PASSWORD=$EMAIL_SMTP_PASSWORD
      - SIGN_IN_PREFILLED=false
      - 'DEBUG_MODE=${DEBUG_MODE:-false}'
      - 'TELEMETRY_ENABLED=${TELEMETRY_ENABLED:-false}'
    depends_on:
      postgres:
        condition: service_healthy
      redis:
        condition: service_healthy
    healthcheck:
      test: 'curl --fail -6 "http://localhost:3000/healthz"'
      interval: 5s
      timeout: 10s
      retries: 25
  worker:
    image: 'twentycrm/twenty:v0.30.0'
    command:
      - yarn
      - 'worker:prod'
    environment:
      - SERVER_URL=$SERVER_URL
      - CORS_ORIGIN=*
      - 'FRONT_BASE_URL=${FRONT_BASE_URL:-$SERVER_URL}'
      - 'PG_DATABASE_URL=postgres://postgres:$SERVICE_PASSWORD_POSTGRES@postgres:5432/default'
      - 'MESSAGE_QUEUE_TYPE=${MESSAGE_QUEUE_TYPE:-pg-boss}'
      - REDIS_HOST=redis
      - REDIS_PORT=6379
      - ENABLE_DB_MIGRATIONS=false
      - STORAGE_TYPE=$STORAGE_TYPE
      - STORAGE_S3_REGION=$STORAGE_S3_REGION
      - STORAGE_S3_NAME=$STORAGE_S3_NAME
      - STORAGE_S3_ENDPOINT=$STORAGE_S3_ENDPOINT
      - STORAGE_S3_ACCESS_KEY_ID=$STORAGE_S3_ACCESS_KEY_ID
      - STORAGE_S3_SECRET_ACCESS_KEY=$STORAGE_S3_SECRET_ACCESS_KEY
      - ACCESS_TOKEN_SECRET=$SERVICE_BASE64_32_ACCESS
      - LOGIN_TOKEN_SECRET=$SERVICE_BASE64_32_LOGIN
      - REFRESH_TOKEN_SECRET=$SERVICE_BASE64_32_REFRESH
      - FILE_TOKEN_SECRET=$SERVICE_BASE64_32_FILE
    depends_on:
      redis:
        condition: service_healthy
      twenty:
        condition: service_healthy
    restart: always
  postgres:
    image: 'twentycrm/twenty-postgres:latest'
    environment:
      - POSTGRES_USER=postgres
      - POSTGRES_PASSWORD=$SERVICE_PASSWORD_POSTGRES
      - POSTGRES_DB=default
    volumes:
      - 'pg-data:/bitnami/postgresql'
    healthcheck:
      test:
        - CMD-SHELL
        - 'pg_isready -U $${POSTGRES_USER} -d $${POSTGRES_DB}'
      interval: 5s
      timeout: 20s
      retries: 10
  redis:
    image: 'redis:latest'
    volumes:
      - 'redis-data:/data'
    healthcheck:
      test:
        - CMD
        - redis-cli
        - ping
      interval: 5s
      timeout: 20s
      retries: 10

[ashayramolia]

i get this in the twenty container

2025-03-28T12:05:08.661426780Z query failed:
2025-03-28T12:05:08.661485700Z DROP FUNCTION IF EXISTS graphql;
2025-03-28T12:05:08.661490308Z CREATE FUNCTION graphql(
2025-03-28T12:05:08.661493635Z "operationName" text default null,
2025-03-28T12:05:08.661496981Z query text default null,
2025-03-28T12:05:08.661500037Z variables jsonb default null,
2025-03-28T12:05:08.661503463Z extensions jsonb default null
2025-03-28T12:05:08.661506619Z )
2025-03-28T12:05:08.661509915Z returns jsonb
2025-03-28T12:05:08.661513161Z language sql
2025-03-28T12:05:08.661516357Z as $$
2025-03-28T12:05:08.661519212Z select graphql.resolve(
2025-03-28T12:05:08.661522278Z query := query,
2025-03-28T12:05:08.661525675Z variables := coalesce(variables, '{}'),
2025-03-28T12:05:08.661528029Z "operationName" := "operationName",
2025-03-28T12:05:08.661530343Z extensions := extensions
2025-03-28T12:05:08.661532537Z );
2025-03-28T12:05:08.661534661Z $$;
2025-03-28T12:05:08.661549519Z
2025-03-28T12:05:08.661762488Z error: error: schema "graphql" does not exist
2025-03-28T12:05:08.667708859Z Failed to perform 'create function graphql': QueryFailedError: schema "graphql" does not exist

[yipfram]

Same here,
The postgres container says this:

          VALIDATOR "logflare_fdw_validator";

2025-04-02 13:42:02.335 GMT [305] ERROR: foreign-data wrapper "s3_fdw" already exists
2025-04-02 13:42:02.335 GMT [305] STATEMENT:
CREATE FOREIGN DATA WRAPPER "s3_fdw"
HANDLER "s3_fdw_handler"
VALIDATOR "s3_fdw_validator";

2025-04-02 13:42:02.344 GMT [305] ERROR: foreign-data wrapper "stripe_fdw" already exists
2025-04-02 13:42:02.344 GMT [305] STATEMENT:
CREATE FOREIGN DATA WRAPPER "stripe_fdw"
HANDLER "stripe_fdw_handler"
VALIDATOR "stripe_fdw_validator";

2025-04-02 13:42:02.364 GMT [305] ERROR: schema "graphql" does not exist at character 306
2025-04-02 13:42:02.364 GMT [305] STATEMENT:
DROP FUNCTION IF EXISTS graphql;
CREATE FUNCTION graphql(
"operationName" text default null,
query text default null,
variables jsonb default null,
extensions jsonb default null
)
returns jsonb
language sql
as $$
select graphql.resolve(
query := query,
variables := coalesce(variables, '{}'),
"operationName" := "operationName",
extensions := extensions
);
$$;

2025-04-02 13:42:22.380 GMT [341] ERROR: extension "pg_graphql" is not available
2025-04-02 13:42:22.380 GMT [341] DETAIL: Could not open extension control file "/opt/bitnami/postgresql/share/extension/pg_graphql.control": No such file or directory.
2025-04-02 13:42:22.380 GMT [341] HINT: The extension must first be installed on the system where PostgreSQL is running.
2025-04-02 13:42:22.380 GMT [341] STATEMENT: CREATE EXTENSION IF NOT EXISTS "pg_graphql"
2025-04-02 13:42:22.447 GMT [341] ERROR: foreign-data wrapper "airtable_fdw" already exists
2025-04-02 13:42:22.447 GMT [341] STATEMENT:
CREATE FOREIGN DATA WRAPPER "airtable_fdw"
HANDLER "airtable_fdw_handler"
VALIDATOR "airtable_fdw_validator";

2025-04-02 13:42:22.468 GMT [341] ERROR: foreign-data wrapper "bigquery_fdw" already exists
2025-04-02 13:42:22.468 GMT [341] STATEMENT:
CREATE FOREIGN DATA WRAPPER "bigquery_fdw"
HANDLER "big_query_fdw_handler"
VALIDATOR "big_query_fdw_validator";

2025-04-02 13:42:22.493 GMT [341] ERROR: foreign-data wrapper "clickhouse_fdw" already exists
2025-04-02 13:42:22.493 GMT [341] STATEMENT:
CREATE FOREIGN DATA WRAPPER "clickhouse_fdw"
HANDLER "click_house_fdw_handler"
VALIDATOR "click_house_fdw_validator";

2025-04-02 13:42:22.501 GMT [341] ERROR: foreign-data wrapper "firebase_fdw" already exists
2025-04-02 13:42:22.501 GMT [341] STATEMENT:
CREATE FOREIGN DATA WRAPPER "firebase_fdw"
HANDLER "firebase_fdw_handler"
VALIDATOR "firebase_fdw_validator";

2025-04-02 13:42:22.511 GMT [341] ERROR: foreign-data wrapper "logflare_fdw" already exists
2025-04-02 13:42:22.511 GMT [341] STATEMENT:
CREATE FOREIGN DATA WRAPPER "logflare_fdw"
HANDLER "logflare_fdw_handler"
VALIDATOR "logflare_fdw_validator";

2025-04-02 13:42:22.520 GMT [341] ERROR: foreign-data wrapper "s3_fdw" already exists
2025-04-02 13:42:22.520 GMT [341] STATEMENT:
CREATE FOREIGN DATA WRAPPER "s3_fdw"
HANDLER "s3_fdw_handler"
VALIDATOR "s3_fdw_validator";

2025-04-02 13:42:22.529 GMT [341] ERROR: foreign-data wrapper "stripe_fdw" already exists
2025-04-02 13:42:22.529 GMT [341] STATEMENT:
CREATE FOREIGN DATA WRAPPER "stripe_fdw"
HANDLER "stripe_fdw_handler"
VALIDATOR "stripe_fdw_validator";

2025-04-02 13:42:22.549 GMT [341] ERROR: schema "graphql" does not exist at character 306
2025-04-02 13:42:22.549 GMT [341] STATEMENT:
DROP FUNCTION IF EXISTS graphql;
CREATE FUNCTION graphql(
"operationName" text default null,
query text default null,
variables jsonb default null,
extensions jsonb default null
)
returns jsonb
language sql
as $$
select graphql.resolve(
query := query,
variables := coalesce(variables, '{}'),
"operationName" := "operationName",
extensions := extensions
);
$$;

[FabianHertwig]

I have created a docker compose file that runs the application, but for now it sets the server to run with root permissions. So that should not be used in production use cases. To fix the issue at its root I have created the following PR #11405

name: twenty

services:
  server:
    image: twentycrm/twenty:${TAG:-latest}
    user: root
    volumes:
      - server-local-data:/app/packages/twenty-server/$${STORAGE_LOCAL_PATH:-.local-storage}
      - docker-data:/app/docker-data
    ports:
      - "3000:3000"
    environment:
      NODE_PORT: 3000
      PG_DATABASE_URL: postgres://${PG_DATABASE_USER:-postgres}:${SERVICE_PASSWORD_DB}@${PG_DATABASE_HOST:-db}:${PG_DATABASE_PORT:-5432}/default
      SERVER_URL: ${SERVICE_FQDN_SERVER_3000}
      REDIS_URL: ${REDIS_URL:-redis://redis:6379}

      STORAGE_TYPE: ${STORAGE_TYPE:-local}
      STORAGE_S3_REGION: ${STORAGE_S3_REGION}
      STORAGE_S3_NAME: ${STORAGE_S3_NAME}
      STORAGE_S3_ENDPOINT: ${STORAGE_S3_ENDPOINT}

      APP_SECRET: ${SERVICE_PASSWORD_APPSECRET}

      SERVICE_FQDN_SERVER_3000:

      MESSAGING_PROVIDER_GMAIL_ENABLED: ${MESSAGING_PROVIDER_GMAIL_ENABLED:-false}
      CALENDAR_PROVIDER_GOOGLE_ENABLED: ${CALENDAR_PROVIDER_GOOGLE_ENABLED:-false}
      AUTH_GOOGLE_CLIENT_ID: ${AUTH_GOOGLE_CLIENT_ID}
      AUTH_GOOGLE_CLIENT_SECRET: ${AUTH_GOOGLE_CLIENT_SECRET}
      AUTH_GOOGLE_CALLBACK_URL: ${AUTH_GOOGLE_CALLBACK_URL}
      AUTH_GOOGLE_APIS_CALLBACK_URL: ${AUTH_GOOGLE_APIS_CALLBACK_URL}

      CALENDAR_PROVIDER_MICROSOFT_ENABLED: ${CALENDAR_PROVIDER_MICROSOFT_ENABLED:-false}
      MESSAGING_PROVIDER_MICROSOFT_ENABLED: ${MESSAGING_PROVIDER_MICROSOFT_ENABLED:-false}
      AUTH_MICROSOFT_ENABLED: ${AUTH_MICROSOFT_ENABLED:-false}
      AUTH_MICROSOFT_CLIENT_ID: ${AUTH_MICROSOFT_CLIENT_ID}
      AUTH_MICROSOFT_CLIENT_SECRET: ${AUTH_MICROSOFT_CLIENT_SECRET}
      AUTH_MICROSOFT_CALLBACK_URL: ${AUTH_MICROSOFT_CALLBACK_URL}
      AUTH_MICROSOFT_APIS_CALLBACK_URL: ${AUTH_MICROSOFT_APIS_CALLBACK_URL}

      EMAIL_FROM_ADDRESS: ${EMAIL_FROM_ADDRESS:-contact@yourdomain.com}
      EMAIL_FROM_NAME: ${EMAIL_FROM_NAME:-"John from YourDomain"}
      EMAIL_SYSTEM_ADDRESS: ${EMAIL_SYSTEM_ADDRESS:-system@yourdomain.com}
      EMAIL_DRIVER: ${EMAIL_DRIVER:-smtp}
      EMAIL_SMTP_HOST: ${EMAIL_SMTP_HOST}
      EMAIL_SMTP_PORT: ${EMAIL_SMTP_PORT:-465}
      EMAIL_SMTP_USER: ${EMAIL_SMTP_USER}
      EMAIL_SMTP_PASSWORD: ${SERVICE_PASSWORD_SMTP}

    depends_on:
      db:
        condition: service_healthy
      redis:
        condition: service_healthy
    healthcheck:
      test: curl --fail http://localhost:3000/healthz
      interval: 5s
      timeout: 5s
      retries: 10
    restart: always

  worker:
    image: twentycrm/twenty:${TAG:-latest}
    volumes:
      - server-local-data:/app/packages/twenty-server/$${STORAGE_LOCAL_PATH:-.local-storage}
    command: ["yarn", "worker:prod"]
    exclude_from_hc: true
    environment:
      PG_DATABASE_URL: postgres://${PG_DATABASE_USER:-postgres}:${SERVICE_PASSWORD_DB}@${PG_DATABASE_HOST:-db}:${PG_DATABASE_PORT:-5432}/default
      SERVER_URL: ${SERVICE_FQDN_SERVER_3000}
      REDIS_URL: ${REDIS_URL:-redis://redis:6379}
      DISABLE_DB_MIGRATIONS: "true" # it already runs on the server

      STORAGE_TYPE: ${STORAGE_TYPE:-local}
      STORAGE_S3_REGION: ${STORAGE_S3_REGION}
      STORAGE_S3_NAME: ${STORAGE_S3_NAME}
      STORAGE_S3_ENDPOINT: ${STORAGE_S3_ENDPOINT}

      APP_SECRET: ${SERVICE_PASSWORD_APPSECRET}

      MESSAGING_PROVIDER_GMAIL_ENABLED: ${MESSAGING_PROVIDER_GMAIL_ENABLED:-false}
      CALENDAR_PROVIDER_GOOGLE_ENABLED: ${CALENDAR_PROVIDER_GOOGLE_ENABLED:-false}
      AUTH_GOOGLE_CLIENT_ID: ${AUTH_GOOGLE_CLIENT_ID}
      AUTH_GOOGLE_CLIENT_SECRET: ${AUTH_GOOGLE_CLIENT_SECRET}
      AUTH_GOOGLE_CALLBACK_URL: ${AUTH_GOOGLE_CALLBACK_URL}
      AUTH_GOOGLE_APIS_CALLBACK_URL: ${AUTH_GOOGLE_APIS_CALLBACK_URL}

      CALENDAR_PROVIDER_MICROSOFT_ENABLED: ${CALENDAR_PROVIDER_MICROSOFT_ENABLED:-false}
      MESSAGING_PROVIDER_MICROSOFT_ENABLED: ${MESSAGING_PROVIDER_MICROSOFT_ENABLED:-false}
      AUTH_MICROSOFT_ENABLED: ${AUTH_MICROSOFT_ENABLED:-false}
      AUTH_MICROSOFT_CLIENT_ID: ${AUTH_MICROSOFT_CLIENT_ID}
      AUTH_MICROSOFT_CLIENT_SECRET: ${AUTH_MICROSOFT_CLIENT_SECRET}
      AUTH_MICROSOFT_CALLBACK_URL: ${AUTH_MICROSOFT_CALLBACK_URL}
      AUTH_MICROSOFT_APIS_CALLBACK_URL: ${AUTH_MICROSOFT_APIS_CALLBACK_URL}

      EMAIL_FROM_ADDRESS: ${EMAIL_FROM_ADDRESS:-contact@yourdomain.com}
      EMAIL_FROM_NAME: ${EMAIL_FROM_NAME:-"John from YourDomain"}
      EMAIL_SYSTEM_ADDRESS: ${EMAIL_SYSTEM_ADDRESS:-system@yourdomain.com}
      EMAIL_DRIVER: ${EMAIL_DRIVER:-smtp}
      EMAIL_SMTP_HOST: ${EMAIL_SMTP_HOST}
      EMAIL_SMTP_PORT: ${EMAIL_SMTP_PORT:-465}
      EMAIL_SMTP_USER: ${EMAIL_SMTP_USER}
      EMAIL_SMTP_PASSWORD: ${SERVICE_PASSWORD_SMTP}

    depends_on:
      db:
        condition: service_healthy
      server:
        condition: service_healthy
    restart: always

  db:
    image: postgres:16
    volumes:
      - db-data:/var/lib/postgresql/data
    environment:
      POSTGRES_USER: ${PG_DATABASE_USER:-postgres}
      POSTGRES_PASSWORD: ${SERVICE_PASSWORD_DB}
    healthcheck:
      test: pg_isready -U ${PG_DATABASE_USER:-postgres} -h localhost -d postgres
      interval: 5s
      timeout: 5s
      retries: 10
    restart: always

  redis:
    image: redis
    restart: always
    healthcheck:
      test: ["CMD", "redis-cli", "ping"]
      interval: 5s
      timeout: 5s
      retries: 10

volumes:
  docker-data:
  db-data:
  server-local-data: