flypod token

flypod token prints the manage_token for a site this machine deployed. Deploy output hides the token by default: it is already saved for the folder, so flypod update, flypod versions, and flypod rollback work without it.

You only need to reveal it to act on an anonymous site from a different machine or folder.

Synopsis

flypod token [--site <id>]

With no flag, flypod reveals the token for the site linked to the current folder. With --site, it looks the site up by id in the local registry.

The token goes to stdout, so it pipes; the warning line goes to stderr.

Flags

Examples

Reveal this folder's token:

flypod token

fk_...

Capture it, or copy it:

TOKEN=$(flypod token)
flypod token | pbcopy

Reveal a remembered site's token by id:

flypod token --site k3p9x2

Notes

• The token is a bearer credential: whoever holds it can update, roll back, or claim that site. Treat it like a password.
• The server stores only a hash of it, so it cannot be rotated or re-issued — only outlived.
• Tokens are only stored for sites deployed from this machine. If the site isn't in the local registry, there is nothing to reveal.
• A claimed site has no stored token: it authenticates with your account session instead. Run flypod login.
• If the site is yours, logging in on the second machine beats copying a token around — a session can be replaced, a manage_token cannot.
• A manage_token does not delete a site. Deletion is account-only, from the signed-in dashboard.