Twenty•6mo ago

I replaced the server url in the test:

test: curl --fail http://${SERVER_URL}/healthz

test: curl --fail http://${SERVER_URL}/healthz

I'm not confortable with the POSTGRES_ADMIN_PASSWORD line without a password. I'm not familiar with this process. When is this password setup? Is it OK to update it after launching the first docker compose? It might be better to setup a password automaticaly. Maybe we could use this command to create a random password here:

LC_ALL=C tr -dc '[:graph:]' </dev/urandom | head -c 18; echo

LC_ALL=C tr -dc '[:graph:]' </dev/urandom | head -c 18; echo

40 Replies

Freebios•6mo ago

Regarding the password, it's indeed a bit of an issue, but it's actually hardcoded for now in the postgres image, we could try to focus on that, or at least create an issue about it @charles The database should be isolated as long as no port is exposed in the docker compose 🙏

greg [iero]•6mo ago

So this .env line is useless?

Freebios•6mo ago

oh wait, I think i'm mistaking with something else, no you right, this one should be randomized ! it's the twenty:twenty user that is problematic

greg [iero]•6mo ago

👍 Makes more sense. You could randomize twenty:twenty during the database initiation step, but I don't see any database init in your script ?

Freebios•6mo ago

It's all in the postgres package https://github.com/twentyhq/twenty/blob/main/packages/twenty-postgres/init.sql

GitHub

twenty/packages/twenty-postgres/init.sql at main · twentyhq/twenty

Building a modern alternative to Salesforce, powered by the community. - twentyhq/twenty

Freebios•6mo ago

It's creating a superuser in order to be able to install pg extensions, it seems that the default root user created by bitnami as insuficient permisions

greg [iero]•6mo ago

Regarding URL, I added FRONT_BASE_URL in .env as I had this error:

server_1  | /app/packages/twenty-server/dist/src/utils/assert.js:12
server_1  |         throw new Error(message);
server_1  |         ^
server_1  | 
server_1  | Error: An instance of EnvironmentVariables has failed the validation:
server_1  |  - property FRONT_BASE_URL has failed the following constraints: isUrl 
server_1  | 
server_1  |     at assert (/app/packages/twenty-server/dist/src/utils/assert.js:12:15)
server_1  |     at Object.validate (/app/packages/twenty-server/dist/src/engine/integrations/environment/environment-variables.js:336:25)
server_1  |     at ConfigModule.forRoot (/app/node_modules/@nestjs/config/dist/config.module.js:67:45)
server_1  |     at Object.<anonymous> (/app/packages/twenty-server/dist/src/engine/integrations/environment/environment.module.js:17:35)
server_1  |     at Module._compile (node:internal/modules/cjs/loader:1256:14)
server_1  |     at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
server_1  |     at Module.load (node:internal/modules/cjs/loader:1119:32)
server_1  |     at Module._load (node:internal/modules/cjs/loader:960:12)
server_1  |     at Module.require (node:internal/modules/cjs/loader:1143:19)
server_1  |     at require (node:internal/modules/cjs/helpers:121:18)

server_1  | /app/packages/twenty-server/dist/src/utils/assert.js:12
server_1  |         throw new Error(message);
server_1  |         ^
server_1  | 
server_1  | Error: An instance of EnvironmentVariables has failed the validation:
server_1  |  - property FRONT_BASE_URL has failed the following constraints: isUrl 
server_1  | 
server_1  |     at assert (/app/packages/twenty-server/dist/src/utils/assert.js:12:15)
server_1  |     at Object.validate (/app/packages/twenty-server/dist/src/engine/integrations/environment/environment-variables.js:336:25)
server_1  |     at ConfigModule.forRoot (/app/node_modules/@nestjs/config/dist/config.module.js:67:45)
server_1  |     at Object.<anonymous> (/app/packages/twenty-server/dist/src/engine/integrations/environment/environment.module.js:17:35)
server_1  |     at Module._compile (node:internal/modules/cjs/loader:1256:14)
server_1  |     at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
server_1  |     at Module.load (node:internal/modules/cjs/loader:1119:32)
server_1  |     at Module._load (node:internal/modules/cjs/loader:960:12)
server_1  |     at Module.require (node:internal/modules/cjs/loader:1143:19)
server_1  |     at require (node:internal/modules/cjs/helpers:121:18)

Freebios•6mo ago

The subtitution wasn't working ? FRONT_BASE_URL: ${FRONT_BASE_URL:-$SERVER_URL} In most configurations it should be the same as SERVER_URL, the only case where you would want it to differ is when you host the frontend on a bucket or some external service Just to make sure, do you use docker compose or docker-compose, i have a hard time understanding how these behavior occurs on version similar to mine 😳

greg [iero]•6mo ago

Nope it was not working. I have SERVER_URL=http://sgl.local:3000 FRONT_BASE_URL=http://sgl.local:3000 I used docker-compose

Freebios•6mo ago

oh, can you run docker-compose version ?

greg [iero]•6mo ago

iero@sgl:~/twenty$ docker compose version Docker Compose version v2.25.0

Freebios•6mo ago

and with docker-compose it's actually two different things

greg [iero]•6mo ago

Sorry iero@sgl:~/twenty$ docker-compose version docker-compose version 1.29.2, build unknown docker-py version: 5.0.3 CPython version: 3.10.12 OpenSSL version: OpenSSL 3.0.2 15 Mar 2022

Freebios•6mo ago

I see now 😄 This one is one major behind 😵

greg [iero]•6mo ago

Ok I try to update it

Gaming

Programming

I replaced the server url in the test: