fix: auto read dns.extra_records_path instead of making it required

Closes HP-538
This commit is contained in:
Aarnav Tale
2026-06-17 11:11:20 -04:00
parent e74e0d4542
commit 2f3a440de5
4 changed files with 10 additions and 10 deletions
+1 -1
View File
@@ -83,7 +83,7 @@ _Default:_ `true`
## settings.headscale.dns_records_path
_Description:_ If you are using `dns.extra_records_path` in your Headscale configuration, you need to set this to the path for Headplane to be able to read the DNS records.
_Description:_ If you are using `dns.extra_records_path` in your Headscale configuration, Headplane reads that path automatically. Set this only when Headplane needs to access the same file at a different path.
Ensure that the file is both readable and writable by the Headplane process.
When using this, Headplane will no longer need to automatically restart Headscale for DNS record changes.
+4 -4
View File
@@ -123,10 +123,10 @@ services:
# Headplane config.yaml file.
- "/path/to/headscale/config.yaml:/etc/headscale/config.yaml"
# If you are using dns.extra_records in Headscale (recommended), you
# should also mount that file here so Headplane can read and write it.
# Ensure that the path matches `headscale.dns_records_path` in your
# Headplane config.yaml file.
# If you are using dns.extra_records_path in Headscale (recommended),
# also mount that file here so Headplane can read and write it. If the
# in-container path differs from Headscale's dns.extra_records_path,
# set `headscale.dns_records_path` in your Headplane config.yaml file.
- "/path/to/headscale/dns_records.json:/etc/headscale/dns_records.json"
# Read-only access to the Docker socket (or a proxy)