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
I have deployed Matomo with a mariaDB in a kubernetes environment. I have set the environment variables for the database and user, but when the pod restarts I still have to click through the 8 easy steps (but I do not have to enter the information) to restart the service. Is there a flag I can set which auto restarts the service, maintains the data already present in the mariaDB, and I don't have to go through clicking the "next" buttons?
The text was updated successfully, but these errors were encountered:
Any update on this? The DB config story is really bad today since instead of the env variables actually populating a config, they just pre-fill the wizard. Ergo if an instance restarts for any reason (which in orchestration is a normal thing) then the next user visiting gets the wizard even though all the DB details are known and the database contents have persisted.
Just ran into the exact same issue here. Database env variables should be used to check if the install was already made without restarting the install process.
I have deployed Matomo with a mariaDB in a kubernetes environment. I have set the environment variables for the database and user, but when the pod restarts I still have to click through the 8 easy steps (but I do not have to enter the information) to restart the service. Is there a flag I can set which auto restarts the service, maintains the data already present in the mariaDB, and I don't have to go through clicking the "next" buttons?
The text was updated successfully, but these errors were encountered: