Update .env.example WIREGUARD_PEERS -> PEERS #116
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Just found this issue and the fix worked for me. First time I've used this and it failed without the fix shown here. |
|
Yep, this also fixed it for me. Thanks. |
|
It's works for me. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #111 and #113
Currently docker-wireguard uses the
PEERSenvironment variable and not theWIREGUARD_PEERSthat's currently in wirehole's docker-compose file. Example: Link to docker-wireguard search for PEERSThis results in new users of wirehole not seeing any QR codes or wireguard configs generated on their first start.
More details: #111 (comment)
This PR fixes the issue by updating
WIREGUARD_PEERStoPEERSto match docker-wireguard.