share
Publish one HTML file at a link that expires.
IWhy I built it
My coding agents often produce a chart or a mockup as one HTML file. I want to open it on my phone or another computer without a deployment for each draft.
An authenticated upload returns a public link and an expiry time. The default lifetime is 24 hours, and the range is one minute to seven days. An authenticated delete removes a page early.
IIHow it fits together
IIIExpiry without a database
Each upload becomes a file with a random name. The server stores the expiry in the file's modification time with os.utime.
Every request checks that time, so an expired page stops at once, even before cleanup runs. A background thread deletes expired files every ten minutes.
IVTreat the page as untrusted
An uploaded page can contain scripts, so it does not get the site's normal origin. The response sends a Content-Security-Policy sandbox without allow-same-origin. The origin becomes opaque, and the page's scripts cannot read cookies or local storage. A page that an agent wrote cannot read my login.
Limits. Anyone with the link can read the page until it expires. The sandbox limits browser privileges. It does not make confidential content safe to publish.