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.

Sign up for GitHub

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

Jump to bottom

Retire pirogue-admin-wireguard after a while #9

Open
CyrilBrulebois opened this issue Aug 23, 2024 · 0 comments
Open

Retire pirogue-admin-wireguard after a while #9

CyrilBrulebois opened this issue Aug 23, 2024 · 0 comments

Comments

@CyrilBrulebois
Copy link
Collaborator

On the very short term, both pirogue-admin and pirogue-admin-wireguard are kept as they are, with a little glue to make them usable together, but at least the latter should go away at some point.

For more details, see ffc9c16
CyrilBrulebois added a commit that referenced this issue Aug 25, 2024
@CyrilBrulebois
Add initial support for pirogue-admin --redeploy --commit.
077e0a5 
To be used in postinst scripts when upgrading: everything is deployed
again using the stored config.yaml except the WireGuard configuration
(see #9). For
now, a warning is logged (without setting a failed return code) if the
config file is missing.

Link: #4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@CyrilBrulebois