ccnet-WI: reconcile hostnames across WI systems #27
Labels
No labels
blocked
borg-backup
ceph
forgejo
in-progress
infra
netdata
nextcloud
p:high
p:low
p:medium
searxng
service-onboard
swarm-nodes
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
copper/ccnet-prod-devops#27
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
docs/ccnet-wi-site.md flags that ccnet-wi-fw's runtime hostname (literally '2') doesn't match its configured hostname (copper-wi-fw), which itself doesn't match the device's actual name used everywhere else — DNS, this repo's docs, etc. (ccnet-wi-fw). Worth checking whether the same drift exists on the other WI systems (trixie, jump, qnap, pbs) while at it.
Scope: set the OS-level hostname on every ccnet-WI system to match its documented/DNS name consistently. Cosmetic, low priority — doesn't affect routing, the WireGuard tunnel, or backups — but worth a single pass so logs and hostname-based tooling aren't confusing later.
Related: docs/ccnet-wi-site.md's ccnet-wi-fw section.