Prastoin Comments - Answer Overflow

    "database:reset": {
      "executor": "nx:run-commands",
      "dependsOn": ["build"],
      "configurations": {
        "no-seed": {
          "cwd": "packages/twenty-server",
          "commands": [
            "nx ts-node-no-deps-transpile-only -- ./scripts/truncate-db.ts",
            "nx ts-node-no-deps-transpile-only -- ./scripts/setup-db.ts",
            "nx database:migrate",
            "nx command-no-deps -- cache:flush"
          ],
          "parallel": false
        },
        "seed": {
          "cwd": "packages/twenty-server",
          "commands": [
            "nx ts-node-no-deps-transpile-only -- ./scripts/truncate-db.ts",
            "nx ts-node-no-deps-transpile-only -- ./scripts/setup-db.ts",
            "nx database:migrate",
            "nx command-no-deps -- cache:flush",
            "nx command-no-deps -- workspace:seed:dev"
          ],
          "parallel": false
        }
      },

    "database:reset": {
      "executor": "nx:run-commands",
      "dependsOn": ["build"],
      "configurations": {
        "no-seed": {
          "cwd": "packages/twenty-server",
          "commands": [
            "nx ts-node-no-deps-transpile-only -- ./scripts/truncate-db.ts",
            "nx ts-node-no-deps-transpile-only -- ./scripts/setup-db.ts",
            "nx database:migrate",
            "nx command-no-deps -- cache:flush"
          ],
          "parallel": false
        },
        "seed": {
          "cwd": "packages/twenty-server",
          "commands": [
            "nx ts-node-no-deps-transpile-only -- ./scripts/truncate-db.ts",
            "nx ts-node-no-deps-transpile-only -- ./scripts/setup-db.ts",
            "nx database:migrate",
            "nx command-no-deps -- cache:flush",
            "nx command-no-deps -- workspace:seed:dev"
          ],
          "parallel": false
        }
      },

14 replies

TTwenty

•Created by Dhruvraj on 4/30/2025 in #❓︱help

Databse reset issue in dev docker server.

As said above:

Edit: Yes I don't think nx script entry was planned to be used in container, ../../ seems broken in the docker container double checking

IMO you have two options either: 1/ ( recommended )

What you can still do is update your local .env database credentials information to be hitting your dev remote database instead of your local

2/ Build your own image that either ships database:reset yarn script entry mocking the nx command or ship nx

14 replies

TTwenty

•Created by Dhruvraj on 4/30/2025 in #❓︱help

Databse reset issue in dev docker server.

Please refer to

14 replies

TTwenty

•Created by Dhruvraj on 4/30/2025 in #❓︱help

Databse reset issue in dev docker server.

That's because unless I'm mistaken nx is not shipped

14 replies

TTwenty

•Created by rubio#1984 on 4/29/2025 in #❓︱help

Changing identifier on custom object

Hello @rubio#1984, you can edit your custom object model identifier using Advanced mode from the object model settings page

2 replies

TTwenty

•Created by Jay Patel on 4/30/2025 in #❓︱help

Database reset on Dev container

Hello @Jay Patel Duplicated of https://discord.com/channels/1130383047699738754/1367036783958822912

2 replies

TTwenty

•Created by Dhruvraj on 4/30/2025 in #❓︱help

Databse reset issue in dev docker server.

If you're running this within a twenty-server container then you indeed need to pass through the yarn nx script, I'm not sure if it has ever been used in a container before 🤔

  "scripts": {
    "nx": "NX_DEFAULT_PROJECT=twenty-server node ../../node_modules/nx/bin/nx.js",
    "start:prod": "node dist/src/main",
    "command:prod": "node dist/src/command/command",
    "worker:prod": "node dist/src/queue-worker/queue-worker",
    "database:init:prod": "npx ts-node ./scripts/setup-db.ts && yarn database:migrate:prod",
    "database:migrate:prod": "npx -y typeorm migration:run -d dist/src/database/typeorm/metadata/metadata.datasource && npx -y typeorm migration:run -d dist/src/database/typeorm/core/core.datasource",
    "clickhouse:migrate:prod": "node dist/src/database/clickhouse/migrations/run-migrations.js",
    "typeorm": "../../node_modules/typeorm/.bin/typeorm"
  },

  "scripts": {
    "nx": "NX_DEFAULT_PROJECT=twenty-server node ../../node_modules/nx/bin/nx.js",
    "start:prod": "node dist/src/main",
    "command:prod": "node dist/src/command/command",
    "worker:prod": "node dist/src/queue-worker/queue-worker",
    "database:init:prod": "npx ts-node ./scripts/setup-db.ts && yarn database:migrate:prod",
    "database:migrate:prod": "npx -y typeorm migration:run -d dist/src/database/typeorm/metadata/metadata.datasource && npx -y typeorm migration:run -d dist/src/database/typeorm/core/core.datasource",
    "clickhouse:migrate:prod": "node dist/src/database/clickhouse/migrations/run-migrations.js",
    "typeorm": "../../node_modules/typeorm/.bin/typeorm"
  },

What you can still do is update your local .env database credentials information to be hitting your dev remote database instead of your local Edit: Yes I don't think nx script entry was planned to be used in container, ../../ seems broken in the docker container double checking

14 replies

TTwenty

•Created by Dhruvraj on 4/30/2025 in #❓︱help

Databse reset issue in dev docker server.

Hey @Dhruvraj please try using npx

14 replies

TTwenty

•Created by Dhruvraj on 4/25/2025 in #❓︱help

Trying to run Postgres spilo container in Ubuntu EC2 Instance

Hey @Dhruvraj Unfortunately we do not support spilo images anymore, to migrate to a postgres 16 database or freeze your database image please refer to https://twenty.com/developers/section/self-hosting/upgrade-guide#(option-2)-database-migration

4 replies

TTwenty

•Created by jose gabriel on 4/26/2025 in #❓︱help

Unable to Reach Back-end

Client is rendered by the back When you do /grapqhl you directly hit the api -> it's UP When you go to /welcome you can see the client tries to hit localhost

27 replies

TTwenty

•Created by jose gabriel on 4/26/2025 in #❓︱help

Unable to Reach Back-end

Just look at your client configuration

27 replies

TTwenty

•Created by jose gabriel on 4/26/2025 in #❓︱help

Unable to Reach Back-end

Tries to hit http://localhost:3000/graphql

27 replies

TTwenty

•Created by jose gabriel on 4/26/2025 in #❓︱help

Unable to Reach Back-end

You can use you browser or tools such as postman etc

27 replies

TTwenty

•Created by jose gabriel on 4/26/2025 in #❓︱help

Unable to Reach Back-end

Please try making a request to your server directly using its exposition url, then share the response The idea here is to scope what service is having issue

27 replies

TTwenty

•Created by jose gabriel on 4/26/2025 in #❓︱help

Unable to Reach Back-end

Please share req result

27 replies

TTwenty

•Created by jose gabriel on 4/26/2025 in #❓︱help

Unable to Reach Back-end

Indeed this log is not normal, for some reason docker-data volumes does not seem to be mounted Are you able to directly hit/reach your api through its exposed url ?

27 replies

TTwenty

•Created by WaveByteIT on 4/27/2025 in #❓︱help

Gmail Calendar error - Cannot read properties of undefined

Sorry hard to go through your logs does workspace member has a value in its firstname column ?

32 replies

TTwenty

•Created by WaveByteIT on 4/27/2025 in #❓︱help

Gmail Calendar error - Cannot read properties of undefined

Ah yeah sorry my bad ! Indeed located at workspace_uuid.workspaceMember might still be usefull to double check the core.user value

32 replies

Gaming

Programming