Versions and their links

Every publish makes a version, numbered from 1 and never edited afterwards. Each one keeps a link that goes on serving what it served the day you sent it.

Every publish is a version

A version carries the message written with it, who published it, when, how many files it holds and how large they are. Nothing rewrites one afterwards: a change is the next version, not an edit of this one.

list_app_versions reads them newest first and pages through with the next_cursor it hands back. read_app_version reads one by its number, with the file listing of what that publish contained.

Version 2 of todo answers at https://todo--v2.reachpad.app/, and version 3 at https://todo--v3.reachpad.app/. The app's own link, https://todo.reachpad.app/, serves whichever version is live.

A version's link keeps working after a later version goes live. Somebody you sent version 2 to last week still sees version 2, which is the difference between showing a colleague what you built and showing them what it has become since.

Access is decided per app rather than per version, so making an app restricted closes its version links too.

Putting an earlier version back

Restore this version, on the app's page, makes an earlier version the live one. It moves a pointer: nothing is rebuilt, nothing is copied, and the version you moved away from keeps its own link and its own number.

A version that failed to build cannot be made live, and neither can one whose files have not finished reaching the app host. The row says which of the two it is.

This page as raw markdown, for an agent or a prompt: /docs/versions.md