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
Do you have a way to keep the database password hidden from the linked app? For security, I would like all linked apps to use their own login. I gather that I can config:set each app with its own DATABASE_URL, however, I noticed there are other variables as well that contain the password. I assume that I can't simply change the password outside of dokku without breaking something (backups for example).
And in the future? If there is a simple future-proof way to keep the credential separate from the app in the container then the end-user can handle any setup requirements that comes along by falling back to config:set and without risking any exposure to the main postgres login.
The text was updated successfully, but these errors were encountered:
Do you have a way to keep the database password hidden from the linked app? For security, I would like all linked apps to use their own login. I gather that I can
config:set
each app with its own DATABASE_URL, however, I noticed there are other variables as well that contain the password. I assume that I can't simply change the password outside of dokku without breaking something (backups for example).DOKKU_POSTGRES_AQUA_URL
DOKKU_POSTGRES_BLACK_URL
DOKKU_POSTGRES_BLUE_URL
And in the future? If there is a simple future-proof way to keep the credential separate from the app in the container then the end-user can handle any setup requirements that comes along by falling back to
config:set
and without risking any exposure to the main postgres login.The text was updated successfully, but these errors were encountered: