Hm so there is one env file which has Cloudron specific configs, that is put into
/run/leantime/envand then the file at
/app/data/envis appended to it on startup: https://git.cloudron.io/cloudron/leantime-app/-/blob/main/start.sh?ref_type=heads#L38
Does that explain the situation you are seeing or is there maybe some bug in the startup script?
Not an expert, but the way I'm reading this(https://git.cloudron.io/cloudron/leantime-app/-/blob/main/start.sh) is:
- copy /app/code/config/sample.env into the app directory
- then update the DB relevant vars and a few more to make the app work
- do this on every startup.
Then yes: this explains the behavior.
However, the question remains: how would I update some of the env vars myself so that they are persisted?
I don't think editing your start.sh would be a good idea, would it?
The latest app package now will retain custom env vars in
/app/data/env. Note that env vars which are required by Cloudron will get overwritten during startup so those cannot be customized. Currently, those are https://git.cloudron.io/cloudron/leantime-app/-/blob/main/start.sh?ref_type=heads#L46