use symlink instead of copy for credentials when using secrets #2875
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.
Breaking change
Proposed change
Type of change
Additional information
openvpn-credentials.txt
nortransmission-credentials.txt
when using secrets #2874relates to #
https://...
Checklist
If user exposed functionality or configuration variables are added/changed:
Notes
I hope adding this section won't break anything and that everything else was filled correctly 🙏.
I don't know if the change from plain text to a symlink file when using secrets should be documented, if so I'll add it.
This config has been tested locally with
VPN works fine but RPC login seems to not be active despite being detected
The
settings.json
does include login infos:(credentials were set to
admin3333:12345
).But I can't remember if its normal here or not (testing in local and accessing via localhost/IP via the same computer), will investigate further.
Couldn't explain it. Marking as ready so someone can see this and maybe exlpain.