starred/headscale
1
0
Fork 0
mirror of https://github.com/juanfont/headscale.git synced 2026-01-11 20:00:28 +01:00
Code Issues 98 Packages Projects Releases 10 Wiki Activity

Add reload and test config commands #59

New Issue
Closed
opened 2025-12-29 01:21:21 +01:00 by adam · 8 comments
adam commented 2025-12-29 01:21:21 +01:00
Owner
Copy Link

Originally created by @0xcd0e on GitHub (Oct 16, 2021).

Like the nginx -t command, it would be nice to verify the config (config.json, derp map, acl) prior to loading it.
Also, like nginx -s reload, it would be nice to reload the configuration during runtime without having to restart the service.

Originally created by @0xcd0e on GitHub (Oct 16, 2021). Like the `nginx -t` command, it would be nice to verify the config (config.json, derp map, acl) prior to loading it. Also, like `nginx -s reload`, it would be nice to reload the configuration during runtime without having to restart the service.
adam added the enhancementstale labels 2025-12-29 01:21:21 +01:00
adam closed this issue 2025-12-29 01:21:22 +01:00
adam commented 2025-12-29 01:21:23 +01:00
Author
Owner
Copy Link

@juanfont commented on GitHub (Oct 17, 2021):

I see the point of this, but I reckon we should develop first an internal API to communicate the CLI with the running service.

Also, bear in mind that given how Tailscale works, restarting the service does not break the connectivity of the nodes.

@juanfont commented on GitHub (Oct 17, 2021): I see the point of this, but I reckon we should develop first an internal API to communicate the CLI with the running service. Also, bear in mind that given how Tailscale works, restarting the service does not break the connectivity of the nodes.
adam commented 2025-12-29 01:21:24 +01:00
Author
Owner
Copy Link

@0xcd0e commented on GitHub (Oct 17, 2021):

Yeah I am aware that this is more of an advanced feature and probably premature in the current state of the project :)

@0xcd0e commented on GitHub (Oct 17, 2021): Yeah I am aware that this is more of an advanced feature and probably premature in the current state of the project :)
adam commented 2025-12-29 01:21:24 +01:00
Author
Owner
Copy Link

@juanfont commented on GitHub (Oct 17, 2021):

You mean the current AMAZING state of the project 🤣

@juanfont commented on GitHub (Oct 17, 2021): You mean the current AMAZING state of the project 🤣
adam commented 2025-12-29 01:21:26 +01:00
Author
Owner
Copy Link

@0xcd0e commented on GitHub (Oct 17, 2021):

Oh no dont get me wrong, I think this project is amazing! I meant the early state of it, not that it was in any way bad :D

@0xcd0e commented on GitHub (Oct 17, 2021): Oh no dont get me wrong, I think this project is amazing! I meant the early state of it, not that it was in any way bad :D
adam commented 2025-12-29 01:21:27 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (Mar 20, 2022):

We should handle signals, so we can do what "traditional" unix apps does and reload the configfile, acls etc on HUP and do graceful shutdown on INT, KILL, etc.

@kradalby commented on GitHub (Mar 20, 2022): We should handle signals, so we can do what "traditional" unix apps does and reload the configfile, acls etc on `HUP` and do graceful shutdown on `INT`, `KILL`, etc.
adam commented 2025-12-29 01:21:27 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (May 31, 2022):

Adding this support for ACLs in #601, in addition to a bit more graceful signal handling for shutdown.

Config reload will have to sit for a bit more, I think we need to do a few rounds of cleanups in the config handling first, to decouple it so this is possible.

@kradalby commented on GitHub (May 31, 2022): Adding this support for ACLs in #601, in addition to a bit more graceful signal handling for shutdown. Config reload will have to sit for a bit more, I think we need to do a few rounds of cleanups in the config handling first, to decouple it so this is possible.
adam commented 2025-12-29 01:21:27 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Oct 13, 2023):

This issue is stale because it has been open for 180 days with no activity.

@github-actions[bot] commented on GitHub (Oct 13, 2023): This issue is stale because it has been open for 180 days with no activity.
adam commented 2025-12-29 01:21:28 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Oct 28, 2023):

This issue was closed because it has been inactive for 14 days since being marked as stale.

@github-actions[bot] commented on GitHub (Oct 28, 2023): This issue was closed because it has been inactive for 14 days since being marked as stale.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
CLI
DERP
DNS
Nix
OIDC
SSH
bug
database
documentation
duplicate
enhancement
faq
good first issue
grants
help wanted
might-come
needs design doc
needs investigation
no-stale-bot
out of scope
performance
policy 📝
pull-request
Mirrored from GitHub Pull Request
 question
regression
routes
stale
tags
tailscale-feature-gap
well described ❤️
wontfix
No Label enhancement stale
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#59
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?