remote-setuplisted
Install: claude install-skill Rhovian/niles
# Remote setup
Set up an always-on relay that also runs Niles. The request path is phone → Tailscale
Serve HTTPS → localhost Caddy → each Niles host's tailnet IPv4 listener. Serve cannot
proxy directly to other tailnet IPs: its dialer bypasses Tailscale routes. No CORS,
Funnel, public listeners or extra authentication headers are needed.
## Inventory before changing anything
1. Collect the relay and host SSH/access details, OS users running Niles, host display
names and routing IDs for the manifest, permitted phone users, and whether push/WoL
are wanted. For push collect a mailto: or https: contact URI. Include the relay as
a host. For WoL collect target MACs and LAN broadcasts from the operator/network.
Ask only for information you cannot discover through authorized access.
2. Read the deployment's existing config and service state. Inspect
`tailscale serve status --json`, Funnel status, Caddy configuration and listeners,
`~/.niles/config.yaml`, and Niles user services on every machine.
Existing remote deployments need a separate migration plan: stop and report the
conflict instead of overwriting services, Serve mounts, push keys or tailnet policy.
An occupied Serve root, chosen port or service path is also a conflict, even if unrelated.
Preserve unrelated config. Do not use `tailscale serve reset`.
Existing path/Unix-socket mounts gate the whole Serve config: even step 13's HTTP
proxy may need sudo. Preserve those mounts and report mis