Closed tony-butchart closed 7 months ago
Some additional testing by bringing up the default docker-compose file shows the app works fine, working backwards from there to my changes to the environmental variables identified that removal of the following variables caused this issue for me:
SMTP_FROMNAME: "Test"
SMTP_FROMADDRESS: "test@domain.tld"
SMTP_HOST: ""
SMTP_PORT: 587
SMTP_USERNAME: ""
SMTP_PASSWORD: ""
SMTP_ENCRYPTION: tls
I wasn't aware of the dependency for SMTP config and had no need for it yet so left it out, adding it back in (as above) resolved my issue.
Happy for this to be closed out if it's not viewed as an issue.
I would say it is unexpected behavior that the app does not fall back to default environment values. In a similar matter, the app breaks with error 500 if I leave out DB_PORT or DB_CHARSET.
Due to the migration of some of the settings, we can remove some of the env vars from the docker-compose file. But some are mandatory. Yes, we can set default values at a different place. I'll think about what's the best approach here. I guess this is a good way, because this is actually the most encountered bug so far and it happens when people remove some stuff from the docker-compose file.
To-do: Default also SMTP settings, because they can also be set up later in the admin dashboard.
Resolved.
Hi,
On a fresh deployment using the provided docker-compose file (with some tweaks, full stack below) I'm getting the following text in large font on the login page:
This error is also seen on the nav bar at the top after login.
I've just run with the defaults in the compose file with a couple of tweaks on the passwords and the volumes, let me know if I'm missing anything critical here:
.env file: