You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This fills some blanks in the setup, but here comes the Problem
Problem
Using this configuration the setup shows the right mail configuration but for the Drivers, Apptimezone , Cachet_beacon, Appurl and Appname it does not work.
Refreshing the page shows the correctly configured values,
looking into the pages sources also shows that the correct configuration is selected.
Trying to continue with doesn't work unless I manually select the values again.
Continuing to the next page shows no value correctly configured:
Looking inside the container both .env file and all environment variables are set correctly. Except for the APP_NAME which is not correctly parsed to docker.
The text was updated successfully, but these errors were encountered:
@manwern I've got a funny feeling Cachet doesn't currently pull those values from the .env into the setup process, although it probably should. I've have a look when I get a moment.
Environment
Dev: Windows 10 2004
Docker: v20.10.2
Cachet: v2.5.0
What I am trying to achieve
I want to minimize user interaction to setup cachet.
What I've tried so far
Setting Environment Variables in the docker-compose.yaml
This fills some blanks in the setup, but here comes the Problem
Problem
Using this configuration the setup shows the right mail configuration but for the Drivers, Apptimezone , Cachet_beacon, Appurl and Appname it does not work.
Refreshing the page shows the correctly configured values,
looking into the pages sources also shows that the correct configuration is selected.
Trying to continue with doesn't work unless I manually select the values again.
Continuing to the next page shows no value correctly configured:
Looking inside the container both .env file and all environment variables are set correctly. Except for the APP_NAME which is not correctly parsed to docker.
The text was updated successfully, but these errors were encountered: