Updated PrivateBin to 1.5.1. Added persistent config volume #958
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.
Changes
By default the config folder is completely empty, so it wont affect existing or new deployments. It will, however, allow us to add our own
conf.php
based on their template.Help Wanted
If there is a way to edit/add config from within CapRover without needing to SSH into the server and manually create a
conf.php
file, please let me know.PrivateBin have configuration file sample that would be perfect as a can use as a placeholder, with everything that is non-default is commented out. This would be the ideal way to manage custom config. 🐈
☑️ Self Check before Merge
npm ci && npm run validate_apps && npm run formatter