Update & rollback
Ship a new version to a site, list its history, and roll back. The day-to-day loop, with no IDs to remember.
After the first deploy, you rarely type a site ID again. flypod links the current folder to its site, so the loop is: edit → update → check → roll back.
Ship a change
Edit your files, then push a new version to the same site:
flypod updateThe new version is built, uploaded, and goes live immediately. Each version is immutable.
Versions are content-addressed: the version id is the hash of the files. Re-running
flypod update with byte-for-byte identical content gives you back the same version
id and adds nothing to the history. The bytes are still uploaded, and the CLI reports
the version as live rather than printing a "no changes" message.
List history
flypod versionsOutput is newest-first, with the live version marked:
v_3f9a1c 2026-06-18T14:02:00Z [live]
v_2b7e44 2026-06-18T11:40:00Z
v_19cd02 2026-06-17T09:15:00ZRoll back
With no argument, flypod rolls back to the previous version:
flypod rollbackTo target an exact version, pass its id or an unambiguous prefix:
flypod rollback v_2b7e44
flypod rollback 2b7eflypod refuses to roll back if the site has only one version, or if the live version is already the oldest.
Multiple projects
If a folder isn't linked, or you're targeting a different site, pass --site:
flypod update --site ab12cd34
flypod versions --site ab12cd34
flypod rollback --site ab12cd34For an anonymous site on a machine that doesn't remember it, authorize the
action with that deploy's manage_token — reveal it with
flypod token on the machine that does:
flypod update --token <manage_token>
flypod rollback --token <manage_token>On your own machine you need none of this: the token is already stored with the
folder link. And if the site is yours, flypod login on the second machine
beats moving a token around.
Self-heal on a stale link
If flypod update gets a 404 (the linked site no longer exists), flypod drops
the stale folder link and tells you to run flypod to deploy fresh. A 401 or
403 means the action is unauthorized; pass --token or log in.
JSON & quiet
update, versions, and rollback all accept --json. update and
rollback also accept -q/--quiet.
flypod update --json
flypod versions --jsonFlags
| Command | Flags |
|---|---|
flypod update [path] | --site <id>, --token <manage_token>, --json, -q |
flypod versions | --site <id>, --json |
flypod rollback [version] | --site <id>, --token <manage_token>, --json, -q |
Next steps
Deploy a site
Deploy a folder or a single file to a live URL, with auto-detection of common build directories and machine-readable output for scripts.
Render Markdown to a docs site
Deploy a folder of Markdown files with no index.html and flypod renders them into a styled docs site with a sidebar and home page.