feat: automatically manage root VPN using wg-portal#31
Open
huytrinhm wants to merge 7 commits into
Open
Conversation
# Conflicts: # .env.sample
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.
This PR adds the wg-portal integration for VPN users.
libs/api/src/wg-portal.tsAPI client for:apps/internal/src/vpn-sync/*module for syncing user VPN state to wg-portal using:username,vpnIpAddress, WireGuard key pair, active/disabled statelibs/common-db/src/schemas/user.schema.tsto queue VPN sync jobs on user changes that may affect VPN statePOST /users/vpn/sync-allto queue a full resync for all userswg_portaltodocker-compose.yaml. The wg_portal container will manage the WireGuard interface on the host and expose the API for syncing peer state. Thevpn-syncservice will run a worker that processes the sync jobs and calls the wg-portal API.