flypod update
Ship a new version of a directory or file to the linked flypod site; the new version becomes live immediately.
flypod update ships a new version to the site linked to the current folder, or to an explicit --site. The new version becomes live immediately.
Synopsis
flypod update [path]The path follows the same auto-detection rules as flypod [path]. flypod resolves the target site from the folder-to-site link saved on the last deploy, or from --site.
A version id is the content hash of the files, so re-running flypod update with byte-identical content returns the same version id and adds no new version — nothing is re-stored. The upload still happens and the CLI still reports the version as live; there is no special "nothing changed" message.
Flags
| Flag | Description |
|---|---|
--site <id> | Target a specific site id instead of the linked one. |
--token <manage_token> | Authorize with a manage_token instead of your session. |
--json | Emit a single JSON object. |
-q, --quiet | Print only the essential value on stdout. |
-h, --help | Print usage and exit. |
Examples
Ship a new version to the linked site:
flypod update ./disthttps://k3p9x2.flypod.devTarget a specific site with a manage token — for an anonymous site on a machine that doesn't remember it. Get the token with flypod token on the machine that does:
flypod update ./dist --site k3p9x2 --token fk_...If the site is yours, flypod login on the second machine is the better path: a session can be replaced, a manage_token cannot.
Notes
- A
401or403response means you are not authorized to update that site. - A
404means the linked site no longer exists. flypod drops the stale link and tells you to runflypodto create a fresh deploy. - Use
flypod versionsto inspect history andflypod rollbackto revert.