feat: allow to declare custom db credentials in install scripts #117
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I removed the hard coded database credentials from the install.sh script and the script included in the manual-installations docs page. Instead I created three new variables (
postgres_user,postgres_db,postgres_password) to declare the credentials, which then will be added asDATABASE_URLto the dokploy container.If no password is defined by the user a random one will be generated with
openssl rand --hex 32.I tested the script on a blank debian 13 server and it worked as expected.
This increases the security of every new Dokploy installation by using a unique password.
This commit solves the issue Dokploy/dokploy#3384 of the dokploy repo.