I replaced the server url in the test:
I replaced the server url in the test:
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:
40 Replies
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 π
So this .env line is useless?
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
π Makes more sense. You could randomize twenty:twenty during the database initiation step, but I don't see any database init in your script ?
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
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
Regarding URL,
I added FRONT_BASE_URL in .env as I had this error:
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 π³Nope it was not working.
I have
SERVER_URL=http://sgl.local:3000
FRONT_BASE_URL=http://sgl.local:3000
I used docker-compose
oh, can you run
docker-compose version
?iero@sgl:~/twenty$ docker compose version
Docker Compose version v2.25.0
and with
docker-compose
it's actually two different thingsSorry
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
I see now π
This one is one major behind π΅
Ok I try to update it