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

[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:

[FelixMalfait]

What is change-vol-ownership?
FYI postgres-spilo is not a requirement for the app as of today, the old postgres image should still work. But we wanted to simplify and use the same image for our cloud offering and for development instead of maintaining 2 separate configs

[FelixMalfait]

I think the issue in your script above could be around spacing/indentation within your multi-line bash script (change-vol-ownership)