Issues / #60
Rename land-shared-one to land-hub-one across all infrastructure
proposed
improvement
Priority: medium
Project: landregistry
Reporter:
21 Mar 2026 19:34
Description
With the hub-and-spoke architecture now formalized (hub.tap.> subject prefix, org forests as spokes connecting via leaf nodes), the server name land-shared-one should be renamed to land-hub-one to match.
Scope:
- Hetzner server name
- DNS records
- Mycelium config references
- LandConfigRegistry: shared role to hub role
- All hardcoded references in code, testbooks, architecture docs
- Landregistry seed data
- Forest config on the server
- Memory files on neoremote
Note: Infrastructure rename, needs careful coordination. IP stays the same so leaf node connections survive if DNS is updated first.
Scope:
- Hetzner server name
- DNS records
- Mycelium config references
- LandConfigRegistry: shared role to hub role
- All hardcoded references in code, testbooks, architecture docs
- Landregistry seed data
- Forest config on the server
- Memory files on neoremote
Note: Infrastructure rename, needs careful coordination. IP stays the same so leaf node connections survive if DNS is updated first.
Comments (1)
nebula
21 Mar 2026 19:45
Grooming: set priority to medium
Nebula's reasoning: This is an infrastructure naming alignment — important for consistency with the hub-and-spoke architecture but not blocking any functionality. The IP stays the same so services remain operational during the rename. Medium priority reflects that this should be done deliberately with coordination across systems, but is not urgent. Title, description, category, and project are all clear and accurate — no changes needed there. The scope list in the description is thorough and well-structured for planning.
Nebula's reasoning: This is an infrastructure naming alignment — important for consistency with the hub-and-spoke architecture but not blocking any functionality. The IP stays the same so services remain operational during the rename. Medium priority reflects that this should be done deliberately with coordination across systems, but is not urgent. Title, description, category, and project are all clear and accurate — no changes needed there. The scope list in the description is thorough and well-structured for planning.