Restoring LAMP app to a different Cloudron instance creates a different mysql password
-
All errors with a Cloudron version 9.0.13
Instead of using variables for username & password, i used hard coded variables in configs. Not good. I know.
Restoring a LAMP app from one instace to a different one, produces a different password.
Expectation: a restore creates an identical environment. Observation: there is a different password for the MYSQL database.
Pronouns: he/him | Primary language: German
-
All errors with a Cloudron version 9.0.13
Instead of using variables for username & password, i used hard coded variables in configs. Not good. I know.Restoring a LAMP app from one instace to a different one, produces a different password.
Expectation: a restore creates an identical environment. Observation: there is a different password for the MYSQL database.
@luckow not sure if that is the right expectation, you have to use env vars. Password is just one or the many config vars of an addon. Addons can change because of user actions. For example, a user changes the SMTP addon address, user changes internal ports of an addon, user changes oidc scopes etc.
In many PaaS setups, they will cycle passwords periodically, so hard-coding will never work even if you don't move instance in the long run. The behavior is the same in all app deployment platforms - heroku, DO app. See https://devcenter.heroku.com/articles/add-ons#config-var-values-can-change for some rationale.
-
G girish has marked this topic as solved on
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login