HydraDistrict Runbook

District infrastructure tracker.

Infrastructure

Overview

HydraDistrict tracks district infrastructure. Districts are infrastructure containers (not owned by anyone) that group venues and services geographically. They define the physical topology of the Hydra network.

Operations

Register a District

hydradistrict register --name <name> --location <city>

List Districts

hydradistrict list

Check Topology

hydradistrict topology

Register District Services

hydradistrict service add --district <name> --type <type> --endpoint <url>

Geo-Proximity

Districts can have latitude and longitude fields for geo-proximity lookups.

Find nearest district

curl "https://hydradistrict.experiencenet.com/api/v1/nearest?lat=50.85&lon=4.35"

Returns the closest district with coordinates and the distance in km.

Get district service URLs

curl "https://hydradistrict.experiencenet.com/api/v1/districts/{id}/services"

Returns a map of service type → URL for that district.

Set coordinates on a district

curl -X PUT -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"name": "EU Nuremberg", "location": "Nuremberg, Germany", "latitude": 49.45, "longitude": 11.08, "provider": "hetzner"}' \
  https://hydradistrict.experiencenet.com/api/v1/districts/eu-nbg1

Key Concepts

• Districts are infrastructure containers: They have no owner, they group venues and services by geographic location
• Topology: Districts define how venues, render nodes, and network services are organized geographically
• YAML store: All district data stored in YAML files (no database)

SSH Access

ssh root@46.224.179.9

Health Check

curl -s https://hydradistrict.experiencenet.com/api/v1/health

Troubleshooting

Service not responding

1. SSH to the server: ssh root@46.224.179.9
2. Check service status: systemctl status hydradistrict
3. Check logs: journalctl -u hydradistrict --since '10 min ago' --no-pager
4. Restart if needed: systemctl restart hydradistrict