Expose a web service running inside a Daytona sandbox through a preview link, including authenticating a private preview URL

Documented steps

1. Start your HTTP service inside the sandbox on any port from 1 to 65535, avoiding port 22222 which is used by the web terminal to access the terminal using preview URLs.
2. Request a standard preview link with `sandbox.get_preview_link(port)`; it returns the URL plus an access token.
3. Note the URL shape: `https://{port}-{sandboxId}.{daytonaProxyDomain}`.
4. For a non-public sandbox, send the returned token on every request in the header `x-daytona-preview-token` — without it the proxy rejects the request.
5. Re-fetch the token after any sandbox restart: the token resets automatically when the sandbox restarts and previously issued standard preview tokens become invalid.
6. When you need a shareable link with no custom headers, create a signed URL with `create_signed_preview_url(port, expires_in_seconds=...)`; the token is embedded in the hostname as `https://{port}-{token}.{daytonaProxyDomain}`.
7. Choose `expires_in_seconds` deliberately — the default is only 60 seconds, the minimum is 1 second and the maximum is 86,400 seconds (24 hours).
8. Rely on signed URLs when the link must survive restarts; unlike standard tokens they remain valid until expiry or explicit revocation.
9. Revoke a signed URL early with `expire_signed_preview_url(port, token)`.
10. Only set the sandbox's public property to true for genuinely non-sensitive services, because that removes authentication from all of its preview links. Official docs: https://www.daytona.io/docs/en/preview, https://www.daytona.io/docs/en/web-terminal