Update & rollback

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 update

The new version is built, uploaded, and goes live immediately. Each version is immutable.

List history

flypod versions

Output 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:00Z

Roll back

With no argument, flypod rolls back to the previous version:

flypod rollback

To target an exact version, pass its id or an unambiguous prefix:

flypod rollback v_2b7e44
flypod rollback 2b7e

flypod 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 ab12cd34

For anonymous sites you don't own, authorize the action with the deploy's manage_token:

flypod update --token <manage_token>
flypod rollback --token <manage_token>

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 --json

Flags

Next steps