CLI reference
The flypod CLI deploys a static directory or file to a public URL with one command, then manages versions, rollbacks, and account ownership.
flypod is a zero-auth static-site deploy primitive. One command ships a directory or single file to a public URL. Logged in, deploys are permanent and owned; anonymous, they live 14 days. Version 0.3.0.
Install
npx flypodOr install globally:
npm i -g flypodThe binary is flypod. The first non-flag positional that matches a known subcommand is dispatched; otherwise the argument is treated as a deploy path. An unknown flag exits with code 2. Success exits 0.
Commands
flypod [path]
Deploy a directory or single file to a public URL.
flypod update
Ship a new version to the linked site; it becomes live.
flypod versions
List a site's versions, newest first.
flypod rollback
Make a previous version live again.
flypod forget
Remove the local folder-to-site memory.
Account commands
login, logout, list, claim, and keys.
flypod install skill
Teach your coding agents how to deploy with flypod.
Global flags
| Flag | Description |
|---|---|
--json | Emit a single machine-readable JSON object on stdout. |
-q, --quiet | Print only the essential value (URL) on stdout. |
-h, --help | Print usage and exit. |
-v, --version | Print the CLI version and exit. |
Environment variables
| Variable | Description |
|---|---|
FLYPOD_TOKEN | Use an account session token for this process (agents / CI). Takes precedence over a saved login. |
DEPLOY_URL | Override the server base URL. Default https://flypod.dev. |
FLYPOD_CONFIG_DIR | Override the config directory. |
NO_COLOR | Disable colored output. |
FORCE_COLOR | Force colored output. |
Configuration files
flypod stores config in a per-user directory, never in your project repo. Override the location with FLYPOD_CONFIG_DIR.
| Platform | Default location |
|---|---|
| macOS | ~/Library/Application Support/flypod |
| Windows | %APPDATA%/flypod |
| Linux | $XDG_CONFIG_HOME/flypod (defaults to ~/.config/flypod) |
Two files are written with mode 0600:
session.json: the account session created byflypod login.projects.json: the folder-to-site registry. LRU-capped at 64 entries; expired entries auto-prune.
Config files are never placed in your project repo. Nothing flypod writes needs to be committed.
Authentication
Connect the CLI through browser device authorization:
flypod loginFor a stateless agent or CI job, provide an existing account session token:
FLYPOD_TOKEN=<session_token> npx flypod ./distFLYPOD_TOKEN takes precedence over a saved login. With neither, the deploy is anonymous. See Account commands.