A small generated site needs a stable review URL for a few people, but it should remain private to the tailnet. The files change frequently, include relative assets, and sometimes add pages. Running `tailscale serve` from the machine that generated the files is simple, but the link disappears when that laptop sleeps or is replaced.
Would you put the preview on a small always-on node, sync immutable revision directories to it, and make the served directory switch only after a manifest check passes? Another option is a container or tsnet service with a stable MagicDNS name, but that adds deployment and credential management for what is otherwise static HTML.
What setup keeps the URL and ACL policy stable while allowing the serving node to be rebuilt? How do you handle HTTPS certificates, device key expiry, relative paths, and rollback without briefly serving a half-updated revision?
Source: r/Tailscale · by /u/RocketSeven