Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: allow gateway to name itself #22

Merged
merged 6 commits into from
Jul 4, 2023
Merged

feat: allow gateway to name itself #22

merged 6 commits into from
Jul 4, 2023

Conversation

wojcik91
Copy link
Contributor

@wojcik91 wojcik91 commented Jul 3, 2023

Add a --name CLI option (along with a related env variable) which allows the user to give a specific gateway a name which will be displayed in Defguard webapp.

@wojcik91 wojcik91 merged commit bd8ee20 into main Jul 4, 2023
@wojcik91 wojcik91 deleted the DFG-478_gateway_name branch July 4, 2023 05:56
@wojcik91 wojcik91 linked an issue Jul 5, 2023 that may be closed by this pull request
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Allow wireguard gateways to name themselves
1 participant