flypod 0.8.0 → 0.10.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE +42 -15
- package/README.md +196 -77
- package/dist/bin/deploy.js +836 -337
- package/dist/{cli-g2wb2hxm.js → cli-198a0gkx.js} +1093 -1008
- package/dist/src/cli/commands.d.ts +19 -2
- package/dist/src/cli/errors.d.ts +68 -0
- package/dist/src/cli/receipt.d.ts +162 -0
- package/dist/src/cli.d.ts +16 -0
- package/dist/src/cli.js +6 -4
- package/dist/src/deploy-source.d.ts +26 -1
- package/dist/src/pack.d.ts +25 -0
- package/package.json +5 -6
package/LICENSE
CHANGED
|
@@ -1,21 +1,48 @@
|
|
|
1
|
-
|
|
1
|
+
flypod CLI — Licence
|
|
2
|
+
Copyright (c) 2026 Sergio Serrano. All rights reserved.
|
|
2
3
|
|
|
3
|
-
|
|
4
|
+
This software is proprietary. It is published on npm so that it can be
|
|
5
|
+
installed and run; publication is not a grant of rights beyond those below.
|
|
4
6
|
|
|
5
|
-
Permission
|
|
6
|
-
of this software and associated documentation files (the "Software"), to deal
|
|
7
|
-
in the Software without restriction, including without limitation the rights
|
|
8
|
-
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
9
|
-
copies of the Software, and to permit persons to whom the Software is
|
|
10
|
-
furnished to do so, subject to the following conditions:
|
|
7
|
+
1. Permission
|
|
11
8
|
|
|
12
|
-
|
|
13
|
-
|
|
9
|
+
You may install, copy and run this package, and use it to deploy content to the
|
|
10
|
+
flypod service, for any purpose including commercial use. You may install it as
|
|
11
|
+
a dependency of your own projects and in your CI systems, and cache it in a
|
|
12
|
+
private registry or lockfile for that purpose.
|
|
13
|
+
|
|
14
|
+
2. Restrictions
|
|
15
|
+
|
|
16
|
+
Except as permitted above, and except where the following cannot lawfully be
|
|
17
|
+
restricted, you may not:
|
|
18
|
+
|
|
19
|
+
a. redistribute, republish or sell this package or a modified copy of it;
|
|
20
|
+
b. modify, adapt or create derivative works from it;
|
|
21
|
+
c. reverse engineer, decompile or disassemble it, other than to the extent
|
|
22
|
+
necessary for interoperability or as permitted by applicable law;
|
|
23
|
+
d. remove or alter this licence or any copyright notice.
|
|
24
|
+
|
|
25
|
+
3. Service
|
|
26
|
+
|
|
27
|
+
Use of the flypod service through this software is additionally governed by the
|
|
28
|
+
flypod Terms of Service and Privacy Policy at https://flypod.dev/terms and
|
|
29
|
+
https://flypod.dev/privacy. Nothing here grants rights to the flypod service
|
|
30
|
+
itself, its source code, or its trademarks.
|
|
31
|
+
|
|
32
|
+
4. Third-party components
|
|
33
|
+
|
|
34
|
+
This package includes third-party open-source components, which remain under
|
|
35
|
+
their own licences. Nothing in this licence limits the rights you have under
|
|
36
|
+
those licences.
|
|
37
|
+
|
|
38
|
+
5. No warranty; no liability
|
|
14
39
|
|
|
15
40
|
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
16
41
|
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
17
|
-
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
|
|
18
|
-
|
|
19
|
-
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR
|
|
20
|
-
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR
|
|
21
|
-
|
|
42
|
+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. TO THE MAXIMUM EXTENT
|
|
43
|
+
PERMITTED BY LAW, THE COPYRIGHT HOLDER SHALL NOT BE LIABLE FOR ANY CLAIM,
|
|
44
|
+
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR
|
|
45
|
+
OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR ITS USE.
|
|
46
|
+
|
|
47
|
+
Nothing in this licence excludes or limits liability where that exclusion or
|
|
48
|
+
limitation is not permitted by applicable law.
|
package/README.md
CHANGED
|
@@ -4,15 +4,11 @@
|
|
|
4
4
|
|
|
5
5
|
```sh
|
|
6
6
|
npx flypod ./dist
|
|
7
|
-
# → https://
|
|
7
|
+
# → https://a3f1c2d4e5b60789.flypod.page
|
|
8
8
|
```
|
|
9
9
|
|
|
10
|
-
No account. No config file. No project to create. Nothing has to be set up
|
|
11
|
-
first — which is why a person, a shell script, a CI job, or a coding agent can
|
|
12
|
-
all finish a deploy unattended, in one call.
|
|
13
|
-
|
|
14
10
|
```
|
|
15
|
-
flypod v0.
|
|
11
|
+
flypod v0.8.0
|
|
16
12
|
|
|
17
13
|
account anonymous · deploy now, flypod login later to keep it
|
|
18
14
|
source dist 12 files · 1.2 MB
|
|
@@ -20,23 +16,40 @@ all finish a deploy unattended, in one call.
|
|
|
20
16
|
|
|
21
17
|
────────────────────────────────────────────────────────
|
|
22
18
|
● Live
|
|
23
|
-
https://
|
|
19
|
+
https://a3f1c2d4e5b60789.flypod.page
|
|
24
20
|
────────────────────────────────────────────────────────
|
|
25
21
|
|
|
26
|
-
|
|
22
|
+
ship a change flypod update new version, same URL
|
|
23
|
+
undo flypod rollback previous version, instantly
|
|
24
|
+
history flypod versions every version, newest first
|
|
27
25
|
|
|
28
|
-
|
|
29
|
-
|
|
30
|
-
|
|
26
|
+
expires 29 Sep 2026 · 14 days · flypod versions
|
|
27
|
+
keep it flypod login drops the expiry from this URL
|
|
28
|
+
and every site on this machine
|
|
31
29
|
```
|
|
32
30
|
|
|
33
|
-
|
|
34
|
-
|
|
35
|
-
|
|
36
|
-
|
|
31
|
+
That URL is real, public, and HTTPS. Send it to someone. (The elapsed time above
|
|
32
|
+
is one illustrative run, not a benchmark — your line shows whatever your deploy
|
|
33
|
+
actually took.)
|
|
34
|
+
|
|
35
|
+
**Nothing has to be set up first.** No account, no config file, no project to
|
|
36
|
+
create, no framework to detect, no dashboard to learn. Which is the interesting
|
|
37
|
+
part: take the human step out of the deploy path and the deploy path becomes
|
|
38
|
+
automatable. A person, a shell script, a CI job, or a coding agent can all
|
|
39
|
+
finish a deploy unattended, in one call, with nothing provisioned in advance.
|
|
40
|
+
|
|
41
|
+
**And nothing is stuck.** Every deploy is a version, so shipping a change keeps
|
|
42
|
+
the same URL and a bad ship is one command from undone:
|
|
43
|
+
|
|
44
|
+
```sh
|
|
45
|
+
flypod update # new version, same URL
|
|
46
|
+
flypod versions # every version, newest first
|
|
47
|
+
flypod rollback # the previous one is live again
|
|
48
|
+
```
|
|
37
49
|
|
|
38
|
-
|
|
39
|
-
|
|
50
|
+
A deploy made without an account is **temporary** — it expires in 14 days, which
|
|
51
|
+
is right for a preview or a demo. `flypod login` makes it **yours**: no expiry,
|
|
52
|
+
listed under `flypod list`.
|
|
40
53
|
|
|
41
54
|
| State | What it means |
|
|
42
55
|
|-------|---------------|
|
|
@@ -52,37 +65,32 @@ That's the whole ownership model. `flypod login` claims **every** anonymous site
|
|
|
52
65
|
this machine remembers, not just the last one — so "deploy now, log in whenever"
|
|
53
66
|
really is the path. You never have to learn what a token is.
|
|
54
67
|
|
|
55
|
-
|
|
68
|
+
Claiming removes the expiry and nothing else. Your site's address does not
|
|
69
|
+
change: every site, temporary or claimed, is served at
|
|
70
|
+
`https://<site-id>.flypod.page`, while `flypod.dev` is the API, the docs, and
|
|
71
|
+
the account pages. Two domains because a deploy needs no account — keeping
|
|
72
|
+
uploaded content off the brand domain means one bad upload can only cost the
|
|
73
|
+
reputation of a domain flypod does not depend on.
|
|
56
74
|
|
|
57
|
-
|
|
58
|
-
|
|
59
|
-
-
|
|
60
|
-
|
|
61
|
-
|
|
62
|
-
- [Flags](#flags)
|
|
63
|
-
- [Environment variables](#environment-variables)
|
|
64
|
-
- [Exit codes](#exit-codes)
|
|
65
|
-
- [How long does a deploy last?](#how-long-does-a-deploy-last)
|
|
66
|
-
- [What flypod doesn't do](#what-flypod-doesnt-do)
|
|
67
|
-
- [Comments on a deployed site](#comments-on-a-deployed-site)
|
|
68
|
-
- [Accounts](#accounts)
|
|
69
|
-
- [What does flypod write to disk?](#what-does-flypod-write-to-disk)
|
|
70
|
-
- [Library API](#library-api)
|
|
71
|
-
- [HTTP API](#http-api)
|
|
75
|
+
Before you start, [flypod.dev/limits](https://flypod.dev/limits) is the honest
|
|
76
|
+
list of what flypod does and does not do — static files only, no server code, no
|
|
77
|
+
build step, 14-day anonymous expiry, and the upload sizes the service ships
|
|
78
|
+
with. It is worth ninety seconds; the short version is
|
|
79
|
+
[below](#what-flypod-doesnt-do).
|
|
72
80
|
|
|
73
81
|
---
|
|
74
82
|
|
|
75
83
|
## Teach your coding agents to deploy
|
|
76
84
|
|
|
77
|
-
|
|
78
|
-
|
|
85
|
+
If you work with a coding agent, this is the command that matters. One run
|
|
86
|
+
writes an [Agent Skill](https://agentskills.io) into your repo, and from then on
|
|
87
|
+
the agent deploys without being told how:
|
|
79
88
|
|
|
80
89
|
```sh
|
|
81
90
|
npx flypod install skill
|
|
82
91
|
```
|
|
83
92
|
|
|
84
|
-
|
|
85
|
-
the two directories every major agent reads:
|
|
93
|
+
It writes into the two directories every major agent reads:
|
|
86
94
|
|
|
87
95
|
| Directory | Read by |
|
|
88
96
|
|-----------|---------|
|
|
@@ -90,7 +98,32 @@ the two directories every major agent reads:
|
|
|
90
98
|
| `.agents/skills/flypod/` | Codex, Cursor, Gemini CLI, GitHub Copilot |
|
|
91
99
|
|
|
92
100
|
Both get the same files, because `SKILL.md` is one open format now rather than a
|
|
93
|
-
different dialect per vendor.
|
|
101
|
+
different dialect per vendor. If you manage skills with the `skills` CLI
|
|
102
|
+
instead, the same payload installs from its public packaging repo:
|
|
103
|
+
|
|
104
|
+
```sh
|
|
105
|
+
npx skills add flypod-dev/flypod-skill
|
|
106
|
+
```
|
|
107
|
+
|
|
108
|
+
**What the agent learns.** A short `SKILL.md` it always loads: the deploy
|
|
109
|
+
command, how to read `--json` and surface the `url`, how to check `warnings`
|
|
110
|
+
before reporting success, why `flypod update` and not a second `flypod`, the
|
|
111
|
+
temporary → `flypod login` → yours model (and that tokens are secrets an agent
|
|
112
|
+
never needs to save), the `FLYPOD_TOKEN` path for headless runs, and the
|
|
113
|
+
static-only boundary so it doesn't pick flypod for an app with server routes.
|
|
114
|
+
|
|
115
|
+
Alongside it, reference docs the agent opens only when the task needs them — so
|
|
116
|
+
they cost nothing until they're wanted:
|
|
117
|
+
|
|
118
|
+
```
|
|
119
|
+
.claude/skills/flypod/
|
|
120
|
+
├── SKILL.md the deploy loop — always loaded
|
|
121
|
+
└── reference/
|
|
122
|
+
├── updates-and-versions.md update, versions, rollback, --site
|
|
123
|
+
├── publishing-markdown.md deploying .md as a rendered site
|
|
124
|
+
├── comments.md review loop on a deployed preview
|
|
125
|
+
└── troubleshooting.md exit codes, warnings, CI, env vars
|
|
126
|
+
```
|
|
94
127
|
|
|
95
128
|
In a terminal you get a checklist:
|
|
96
129
|
|
|
@@ -108,28 +141,6 @@ In a terminal you get a checklist:
|
|
|
108
141
|
Piped, or run by an agent, it's non-interactive and writes both — so it drops
|
|
109
142
|
cleanly into a setup script.
|
|
110
143
|
|
|
111
|
-
**What it contains.** A short `SKILL.md` the agent always loads: the deploy
|
|
112
|
-
command, how to read `--json` and surface the `url`, why `flypod update` and not
|
|
113
|
-
a second `flypod`, the temporary → `flypod login` → yours model (and that tokens
|
|
114
|
-
are secrets an agent never needs to save), the `FLYPOD_TOKEN` path for headless
|
|
115
|
-
runs, and the static-only boundary so an agent doesn't pick flypod for an app
|
|
116
|
-
with server routes.
|
|
117
|
-
|
|
118
|
-
Alongside it, reference docs the agent opens only when the task needs them —
|
|
119
|
-
so they cost nothing until they're wanted:
|
|
120
|
-
|
|
121
|
-
```
|
|
122
|
-
.claude/skills/flypod/
|
|
123
|
-
├── SKILL.md the deploy loop — always loaded
|
|
124
|
-
└── reference/
|
|
125
|
-
├── updates-and-versions.md update, versions, rollback, --site
|
|
126
|
-
├── publishing-markdown.md deploying .md as a rendered site
|
|
127
|
-
├── comments.md review loop on a deployed preview
|
|
128
|
-
└── troubleshooting.md exit codes, warnings, CI, env vars
|
|
129
|
-
```
|
|
130
|
-
|
|
131
|
-
**Flags:**
|
|
132
|
-
|
|
133
144
|
```sh
|
|
134
145
|
flypod install skill # both directories
|
|
135
146
|
flypod install skill --claude # just the Claude Code skill
|
|
@@ -152,6 +163,24 @@ earlier version, the command points them out and leaves the removal to you.
|
|
|
152
163
|
|
|
153
164
|
---
|
|
154
165
|
|
|
166
|
+
## Contents
|
|
167
|
+
|
|
168
|
+
- [How do I deploy a folder?](#how-do-i-deploy-a-folder)
|
|
169
|
+
- [How do I ship a change to the same site?](#how-do-i-ship-a-change-to-the-same-site)
|
|
170
|
+
- [How do I roll back?](#how-do-i-roll-back)
|
|
171
|
+
- [How do I use flypod from an agent or CI?](#how-do-i-use-flypod-from-an-agent-or-ci)
|
|
172
|
+
- [Deploying Markdown](#deploying-markdown)
|
|
173
|
+
- [Flags](#flags)
|
|
174
|
+
- [Environment variables](#environment-variables)
|
|
175
|
+
- [Exit codes](#exit-codes)
|
|
176
|
+
- [How long does a deploy last?](#how-long-does-a-deploy-last)
|
|
177
|
+
- [What flypod doesn't do](#what-flypod-doesnt-do)
|
|
178
|
+
- [Comments on a deployed site](#comments-on-a-deployed-site)
|
|
179
|
+
- [Accounts](#accounts)
|
|
180
|
+
- [What does flypod write to disk?](#what-does-flypod-write-to-disk)
|
|
181
|
+
- [Library API](#library-api)
|
|
182
|
+
- [HTTP API](#http-api)
|
|
183
|
+
|
|
155
184
|
## How do I deploy a folder?
|
|
156
185
|
|
|
157
186
|
Point `flypod` at the folder of built files. It zips them, uploads them, and
|
|
@@ -170,6 +199,9 @@ With no path, flypod tries these in order and takes the first one that exists
|
|
|
170
199
|
dist · build · out · .output/public · .vercel/output/static · public · _site
|
|
171
200
|
```
|
|
172
201
|
|
|
202
|
+
The URL is always printed alone on **stdout**; everything else goes to stderr.
|
|
203
|
+
`URL=$(npx flypod -q)` and `npx flypod | tee url.txt` both work.
|
|
204
|
+
|
|
173
205
|
`flypod` always creates a **new site**. To ship changes to a site you already
|
|
174
206
|
made, use [`flypod update`](#how-do-i-ship-a-change-to-the-same-site) — not
|
|
175
207
|
`flypod` again.
|
|
@@ -259,7 +291,9 @@ flypod rollback # previous version becomes live
|
|
|
259
291
|
flypod rollback <id> # a specific version — full id or an unambiguous prefix
|
|
260
292
|
```
|
|
261
293
|
|
|
262
|
-
`versions` prints tab-separated `version_id created_at live` on stdout
|
|
294
|
+
`versions` prints tab-separated `version_id created_at live` on stdout,
|
|
295
|
+
with `created_at` as a readable UTC date. `--json` keeps it as epoch
|
|
296
|
+
milliseconds, so scripts and agents parse the same value they always did.
|
|
263
297
|
`--json` is supported on `update`, `versions`, and `rollback` for stable,
|
|
264
298
|
scriptable output.
|
|
265
299
|
|
|
@@ -275,8 +309,8 @@ npx flypod ./dist --json
|
|
|
275
309
|
```json
|
|
276
310
|
{
|
|
277
311
|
"ok": true,
|
|
278
|
-
"url": "https://
|
|
279
|
-
"site_id": "
|
|
312
|
+
"url": "https://a3f1c2d4e5b60789.flypod.page",
|
|
313
|
+
"site_id": "a3f1c2d4e5b60789",
|
|
280
314
|
"version_id": "…",
|
|
281
315
|
"expires_at": 1782929906088,
|
|
282
316
|
"manage_token": "…",
|
|
@@ -284,15 +318,57 @@ npx flypod ./dist --json
|
|
|
284
318
|
"source": "dist",
|
|
285
319
|
"files": 12,
|
|
286
320
|
"bytes": 1234567,
|
|
287
|
-
"elapsed_ms": 812
|
|
321
|
+
"elapsed_ms": 812,
|
|
322
|
+
"healed": ["spa-fallback"],
|
|
323
|
+
"warnings": []
|
|
288
324
|
}
|
|
289
325
|
```
|
|
290
326
|
|
|
327
|
+
**Read `warnings` before you report success.** A deploy can exit 0 and still
|
|
328
|
+
serve a site that's broken for visitors, and this array is the only signal that
|
|
329
|
+
says so. Each entry carries a `code` and a `fix_recipe` naming the change to
|
|
330
|
+
make — `missing-index` when nothing is served at `/`, `not-spa` when the build
|
|
331
|
+
ships scripts alongside visible body content, so client-side routing fallback
|
|
332
|
+
stays off and deep links will 404 on refresh.
|
|
333
|
+
|
|
334
|
+
`healed` is the other half: problems flypod fixed on your behalf. `spa-fallback`
|
|
335
|
+
there means it recognised a single-page app, so unknown paths serve `index.html`
|
|
336
|
+
and client-side routing works with nothing configured.
|
|
337
|
+
|
|
338
|
+
For an agent, that pair is a closed loop — deploy, read the receipt, apply the
|
|
339
|
+
`fix_recipe`, `flypod update` — without a human in it.
|
|
340
|
+
|
|
291
341
|
`expires_at` is epoch **milliseconds** while the site is temporary, and `null`
|
|
292
342
|
once it's yours. On an authenticated deploy `owner_account_id` is present and
|
|
293
343
|
`claim_token` is absent — keys that don't apply are omitted rather than emitted
|
|
294
|
-
as `null`.
|
|
295
|
-
|
|
344
|
+
as `null`. `link_saved` says whether `flypod update` will work from this folder
|
|
345
|
+
with no flags; when it is `false` the `next` commands carry `--site <id>`.
|
|
346
|
+
|
|
347
|
+
**Every failure is JSON too**, on every verb, so `--json` is safe to parse
|
|
348
|
+
unconditionally:
|
|
349
|
+
|
|
350
|
+
```json
|
|
351
|
+
{ "ok": false, "code": "rate_limited", "error": "Too many requests from this network right now.", "fix": "Wait a minute and retry the same command.", "retry_after_s": 30 }
|
|
352
|
+
```
|
|
353
|
+
|
|
354
|
+
Branch on `code` — it is stable; `error` is prose and may change; `fix`, when
|
|
355
|
+
present, is the literal next step. The codes: `no_build_dir`, `no_files`,
|
|
356
|
+
`no_site`, `not_signed_in`, `unauthorized`, `token_rejected`, `site_gone`,
|
|
357
|
+
`invalid_upload`, `too_large`, `blocked`, `challenge_required`, `rate_limited`,
|
|
358
|
+
`server_error`, `network`, `usage`, `unknown_flag`, and the login codes below.
|
|
359
|
+
The [exit code](#exit-codes) follows the code, never the verb.
|
|
360
|
+
|
|
361
|
+
A credential that is sent but not accepted (an expired `FLYPOD_TOKEN`, say)
|
|
362
|
+
fails the deploy with `token_rejected` — it never silently falls back to an
|
|
363
|
+
anonymous 14-day site.
|
|
364
|
+
|
|
365
|
+
**Signing in from an agent.** `flypod login` needs a browser, so an agent runs
|
|
366
|
+
`flypod login --json`: it prints the URL, the confirmation code, and a
|
|
367
|
+
`device_code`, then exits at once (`interactive_login_required`, exit 2) instead
|
|
368
|
+
of waiting. Hand the URL and code to the user; once they confirm, finish with
|
|
369
|
+
`flypod login --device-code <device_code>` — that polls once and either saves
|
|
370
|
+
the session (`{"ok": true, "logged_in": true}`) or reports
|
|
371
|
+
`authorization_pending` (exit 4) to try again.
|
|
296
372
|
|
|
297
373
|
Or capture just the URL:
|
|
298
374
|
|
|
@@ -313,6 +389,32 @@ token in the environment:
|
|
|
313
389
|
FLYPOD_TOKEN=<session-token> npx flypod ./dist --json
|
|
314
390
|
```
|
|
315
391
|
|
|
392
|
+
## Deploying Markdown
|
|
393
|
+
|
|
394
|
+
Point flypod at `.md` files and it renders them into a browsable site — no
|
|
395
|
+
static-site generator, no theme, no build step.
|
|
396
|
+
|
|
397
|
+
```sh
|
|
398
|
+
npx flypod ./report.md # one document
|
|
399
|
+
npx flypod ./notes # a folder of documents
|
|
400
|
+
```
|
|
401
|
+
|
|
402
|
+
Rendering kicks in when the deploy has **no `index.html` at its root** and at
|
|
403
|
+
least one `.md`, `.markdown`, or `.mdx` file. That condition is deliberate: a
|
|
404
|
+
real static site that happens to ship a stray `README.md` is never hijacked.
|
|
405
|
+
|
|
406
|
+
You get one page per document, navigation across all of them, a title from the
|
|
407
|
+
first `#` heading, light and dark themes applied before first paint, and
|
|
408
|
+
sanitized HTML — inline `<script>`, `on*` attributes, and `javascript:` links
|
|
409
|
+
are stripped.
|
|
410
|
+
|
|
411
|
+
The Markdown sources survive. A browser opening the URL gets the styled page; a
|
|
412
|
+
client that asks for Markdown gets the original back from the same URL:
|
|
413
|
+
|
|
414
|
+
```sh
|
|
415
|
+
curl -H 'Accept: text/markdown' https://a3f1c2d4e5b60789.flypod.page/guide.html
|
|
416
|
+
```
|
|
417
|
+
|
|
316
418
|
## Flags
|
|
317
419
|
|
|
318
420
|
Deploy flags:
|
|
@@ -352,13 +454,15 @@ setups should use `FLYPOD_TOKEN`.
|
|
|
352
454
|
|
|
353
455
|
## Exit codes
|
|
354
456
|
|
|
457
|
+
The exit code follows the failure's `code`, so the table is true for every verb:
|
|
458
|
+
|
|
355
459
|
| Code | Meaning |
|
|
356
460
|
|------|---------|
|
|
357
461
|
| `0` | Success |
|
|
358
|
-
| `1` | Runtime error — no build folder,
|
|
359
|
-
| `2` | Usage error — unknown flag, unknown subcommand, missing argument |
|
|
360
|
-
| `3` |
|
|
361
|
-
| `4` |
|
|
462
|
+
| `1` | Runtime error the caller can act on — no build folder, site gone, upload rejected or blocked |
|
|
463
|
+
| `2` | Usage error — unknown flag, unknown subcommand, missing argument, or a login that needs a browser (`--json`) |
|
|
464
|
+
| `3` | Auth — not signed in, credential refused (`unauthorized`, `token_rejected`), or sign-in denied |
|
|
465
|
+
| `4` | Retryable — rate limited, server 5xx, network failure, or a sign-in still pending |
|
|
362
466
|
| `130` | The interactive skill picker was cancelled; nothing was written |
|
|
363
467
|
|
|
364
468
|
## How long does a deploy last?
|
|
@@ -385,16 +489,21 @@ login` is the path you want.)
|
|
|
385
489
|
|
|
386
490
|
## What flypod doesn't do
|
|
387
491
|
|
|
388
|
-
Stated up front, as design decisions, so nothing is a surprise on day two.
|
|
492
|
+
Stated up front, as design decisions, so nothing is a surprise on day two. The
|
|
493
|
+
long version, with the reasoning attached, is at
|
|
494
|
+
[flypod.dev/limits](https://flypod.dev/limits).
|
|
389
495
|
|
|
390
496
|
- **Static files only.** HTML, CSS, JS, images, Markdown, assets. If a browser
|
|
391
497
|
can render it, it ships.
|
|
392
498
|
- **No server code.** No functions, no edge middleware, no request handlers.
|
|
393
499
|
- **No databases.** Nothing stateful behind the site.
|
|
394
|
-
- **No build step.** flypod ships your build *output*;
|
|
395
|
-
bundler
|
|
396
|
-
|
|
397
|
-
|
|
500
|
+
- **No build step, and no CI/CD integration.** flypod ships your build *output*;
|
|
501
|
+
it never runs your bundler and has no opinions about your git history. Point
|
|
502
|
+
it at `dist/`, not at the project root.
|
|
503
|
+
- **No custom domains, and no chosen subdomain.** Every site lives at
|
|
504
|
+
`<site-id>.flypod.page`, where the 16-hex site id is flypod's to pick. There
|
|
505
|
+
is no DNS change to make, which is exactly why a script or an agent can
|
|
506
|
+
produce a working URL unattended.
|
|
398
507
|
- **No dashboard you're expected to live in.** The CLI and the URL are the
|
|
399
508
|
product.
|
|
400
509
|
- **Not permanent by default.** Anonymous deploys last 14 days.
|
|
@@ -425,6 +534,10 @@ flypod comments reopen <site> <thread_id>
|
|
|
425
534
|
Modes: `anonymous` (anyone can comment), `passcode` (a shared passcode gates
|
|
426
535
|
posting), `approved` (comments appear after review).
|
|
427
536
|
|
|
537
|
+
Reviewers need no account in `anonymous` mode, which is the point: ship a
|
|
538
|
+
preview, collect what came back as JSON, fix, `flypod update`, resolve the
|
|
539
|
+
thread.
|
|
540
|
+
|
|
428
541
|
## Accounts
|
|
429
542
|
|
|
430
543
|
Accounts are the upgrade, not the entry fee. Everything above works without
|
|
@@ -502,6 +615,8 @@ interface DeployResult {
|
|
|
502
615
|
claim_token?: string; // anonymous only — attaches the site to an account
|
|
503
616
|
manage_token: string; // redeploy / rollback / claim
|
|
504
617
|
owner_account_id?: string; // present on authenticated deploys
|
|
618
|
+
healed?: string[]; // problems the deploy pipeline fixed for you
|
|
619
|
+
warnings?: Array<{ code: string; fix_recipe: string }>;
|
|
505
620
|
next_actions: unknown[];
|
|
506
621
|
}
|
|
507
622
|
```
|
|
@@ -553,6 +668,10 @@ curl -X POST https://flypod.dev/sites/<id>/rollback \
|
|
|
553
668
|
|
|
554
669
|
---
|
|
555
670
|
|
|
556
|
-
Docs: [flypod.dev](https://flypod.dev) · [docs.flypod.dev](https://docs.flypod.dev)
|
|
671
|
+
Docs: [flypod.dev](https://flypod.dev) · [docs.flypod.dev](https://docs.flypod.dev) ·
|
|
672
|
+
[limits](https://flypod.dev/limits) · [report abuse](https://flypod.dev/abuse)
|
|
557
673
|
|
|
558
|
-
|
|
674
|
+
flypod is a hosted service. This package is published so it can be installed and
|
|
675
|
+
run — see [`LICENSE`](./LICENSE) for the terms. The agent-skill files it writes
|
|
676
|
+
are MIT-licensed separately, at
|
|
677
|
+
[flypod-dev/flypod-skill](https://github.com/flypod-dev/flypod-skill).
|