[bug]: variable in plane.env doesn't work (POSTGRES_PASSWORD, SECRET_KEY)

[loutig]

Is there an existing issue for this?

• [X] I have searched the existing issues

Current behavior

i figured it out that i can't use my own password and secret key in the plane.env. If i set a my own POSTGRES_PASSWORD, then the DB creation not working. If i set my own SECRET_KEY, then i can't upload anything to minio.

Have you hard-coded all the thing ??

Steps to reproduce

1. install plane with setup.sh
2. modify plane.env and set a password to POSTGRES_PASSWORD
3. start plane with setup.sh

Environment

Production

Browser

Google Chrome

Variant

Self-hosted

Version

v0.21-dev

[igmarketing]

I really wanted to like this but a simply bug like this and still not fixed since 2 months? Wow... we can't even install the app as your docker script is broken.

[pablohashescobar]

@loutig, @igmarketing sorry for missing this.

if you change the postgres password you have to update update the DATABASE_URL environment as well as this is used by the application to connect to database.

regarding the minio issue can you share the network log when you are trying to upload the image.

on the install script part what is the issue you are facing @igmarketing ?

[dassels]

Anybody still having trouble setting a password for postgres? I tried updating the DATABASE_URL as mentioned here, which btw is DATABASE_URL=postgresql://${POSTGRES_USER}:${POSTGRES_PASSWORD}@${PGHOST}/${PGDATABASE}. When starting the container, it fails with:

migrator-1 | File "/usr/local/lib/python3.12/urllib/parse.py", line 182, in port migrator-1 | raise ValueError(f"Port could not be cast to integer value as {port!r}") migrator-1 | ValueError: Port could not be cast to integer value as 'h+'