readme: clarify that 127.0.0.1 should be used over localhost#6
Open
colemickens wants to merge 1 commit into
Open
readme: clarify that 127.0.0.1 should be used over localhost#6colemickens wants to merge 1 commit into
colemickens wants to merge 1 commit into
Conversation
Contributor
Author
|
fixes #5 |
BusyJay
reviewed
Mar 16, 2021
| If you have customized extra socket localtion, you can append the path as second parameter. | ||
| If you have customized extra socket location, you can append the path as second parameter. | ||
|
|
||
| **NOTE**: Ensure that you listen on and forward to `127.0.0.1:<port>` as opposed to `localhost:<port>`. The latter will cause `gpg-bridge` to listen |
Owner
There was a problem hiding this comment.
I'm not sure if it's true for all users. How about adding it as a hint or FAQ?
|
This branch has conflicts that must be resolved |
This file contains hidden or 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
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 #5