flypod comments
Turn comments on or off for a site, and read, post, resolve, and reopen threads from the terminal.
flypod comments manages the comment layer on a deployed site: the setting itself, and the threads visitors leave. Turning comments on requires an account, so run flypod login first.
Synopsis
flypod comments enable [--site <id>] [--mode anonymous|passcode|approved] [--passcode <s>]
flypod comments mode <anonymous|passcode|approved> [--site <id>] [--passcode <s>]
flypod comments off [--site <id>]
flypod comments list [<site>] [--page <p>] [--open|--resolved|--all] [--limit N] [--json]
flypod comments show [<site>] <thread_id>
flypod comments post [<site>] --page <path> --target <json> --body <text>
flypod comments resolve [<site>] <thread_id>
flypod comments reopen [<site>] <thread_id>The site defaults to the one linked to the current folder. With no site given and no link, a verb fails with no_site. For show, resolve, and reopen, the number of positionals decides: two are <site> <thread_id>, one is the thread in the linked site.
Verbs
| Verb | What it does |
|---|---|
enable | Turn comments on for an existing site, in anonymous mode unless --mode says otherwise. To turn them on at deploy time instead, pass --comments to flypod. |
mode | Turn comments on and set who can comment: anonymous, passcode (with --passcode <s>), or approved. |
off | Turn comments off. Existing threads are kept. |
list | List threads, one JSON object per line on stdout. --page narrows to one page, --open/--resolved/--all by status, --limit N caps the count. Without --json, a count is also printed on stderr. |
show | Print one thread with its replies, as JSON on stdout. |
post | Add a comment to a page (--page), anchored by --target (a W3C selector, as JSON), with --body. Prints the created comment as JSON. Invalid --target JSON fails with usage. |
resolve | Mark a thread resolved. |
reopen | Reopen a resolved thread. |
--mode also accepts the older names open (now anonymous) and review / members (now approved); the server maps them.
Authentication
enable, mode, off, post, resolve, and reopen need your account: a saved flypod login or FLYPOD_TOKEN. Without one they fail with not_signed_in (exit 3). They never use the manage_token this machine stored for a site. list and show send whatever credential you have and let the server decide.
Output
With --json, enable and mode print {"ok":true,"site_id":"…","mode":"…"}, off prints {"ok":true,"site_id":"…","enabled":false}, and resolve / reopen print {"ok":true,…} with the server's thread fields. Without --json, those verbs confirm on stderr.
Errors
Failures use the same shape and exit codes as every other command; see Errors and exit codes. A verb that does not exist fails with unknown_command (exit 2), naming the closest verb. --help on any verb prints its usage and never runs it.