Repository navigation
Conversation
Owner
Author
|
Closed: a different implementation was chosen, an Xray backend driven by the operator's Xray config (#3). |
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
1 participant
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.
usher manages AmneziaWG only. This adds Xray as a second backend: usher reads VLESS Reality inbounds through Xray's own gRPC API on a unix socket, keeps one UUID per user and inbound in
users.json, reconciles users withHandlerService, and writes onevless://link per user and inbound intoclients/.Breaking:
USHER_AWG_SOCKETbecomes required in the environment, andusers.jsonmoves to version 2, which the previous image cannot read.The work follows
docs/plans/20261007-xray-driver.md; this PR is a draft until every task is done. CI runs the awg and Xray e2e suites on each push.