flypod 0.10.0 → 0.11.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/README.md +164 -35
- package/dist/bin/deploy.js +271 -156
- package/dist/{cli-198a0gkx.js → cli-nqpgfpnm.js} +31 -9
- package/dist/src/cli/commands.d.ts +10 -0
- package/dist/src/cli/errors.d.ts +8 -2
- package/dist/src/cli/receipt.d.ts +102 -68
- package/dist/src/cli/screen.d.ts +43 -0
- package/dist/src/cli.js +1 -1
- package/dist/src/deploy-source.d.ts +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -8,24 +8,13 @@ npx flypod ./dist
|
|
|
8
8
|
```
|
|
9
9
|
|
|
10
10
|
```
|
|
11
|
-
|
|
11
|
+
✓ Deployed in 0.9s · 12 files · 1.2 MB
|
|
12
12
|
|
|
13
|
-
account anonymous · deploy now, flypod login later to keep it
|
|
14
|
-
source dist 12 files · 1.2 MB
|
|
15
|
-
✓ Deployed in 0.9s
|
|
16
|
-
|
|
17
|
-
────────────────────────────────────────────────────────
|
|
18
|
-
● Live
|
|
19
13
|
https://a3f1c2d4e5b60789.flypod.page
|
|
20
|
-
────────────────────────────────────────────────────────
|
|
21
|
-
|
|
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
|
|
25
14
|
|
|
26
|
-
expires
|
|
27
|
-
keep it
|
|
28
|
-
|
|
15
|
+
expires 19 Oct 2026 in 14 days
|
|
16
|
+
keep it flypod login free · removes the expiry
|
|
17
|
+
update flypod update publishes a new version · same URL
|
|
29
18
|
```
|
|
30
19
|
|
|
31
20
|
That URL is real, public, and HTTPS. Send it to someone. (The elapsed time above
|
|
@@ -169,6 +158,8 @@ earlier version, the command points them out and leaves the removal to you.
|
|
|
169
158
|
- [How do I ship a change to the same site?](#how-do-i-ship-a-change-to-the-same-site)
|
|
170
159
|
- [How do I roll back?](#how-do-i-roll-back)
|
|
171
160
|
- [How do I use flypod from an agent or CI?](#how-do-i-use-flypod-from-an-agent-or-ci)
|
|
161
|
+
- [How do I deploy from a chat app?](#how-do-i-deploy-from-a-chat-app)
|
|
162
|
+
- [How are files served?](#how-are-files-served)
|
|
172
163
|
- [Deploying Markdown](#deploying-markdown)
|
|
173
164
|
- [Flags](#flags)
|
|
174
165
|
- [Environment variables](#environment-variables)
|
|
@@ -199,8 +190,14 @@ With no path, flypod tries these in order and takes the first one that exists
|
|
|
199
190
|
dist · build · out · .output/public · .vercel/output/static · public · _site
|
|
200
191
|
```
|
|
201
192
|
|
|
202
|
-
The URL is
|
|
203
|
-
`URL=$(npx flypod
|
|
193
|
+
The URL is printed alone on **stdout** whenever stdout is not your terminal;
|
|
194
|
+
everything else goes to stderr. So `URL=$(npx flypod)` and
|
|
195
|
+
`npx flypod | tee url.txt` both get just the URL, and at a terminal you see it
|
|
196
|
+
once, in the receipt, rather than twice.
|
|
197
|
+
|
|
198
|
+
Every command's output uses the same few shapes: a `✓` line for what
|
|
199
|
+
happened, the URL on a line of its own, a small grid of next steps, `!` for
|
|
200
|
+
something to look at, and `✗` with the fix underneath when it did not work.
|
|
204
201
|
|
|
205
202
|
`flypod` always creates a **new site**. To ship changes to a site you already
|
|
206
203
|
made, use [`flypod update`](#how-do-i-ship-a-change-to-the-same-site) — not
|
|
@@ -224,6 +221,16 @@ flypod update # ship changes → v2 (now live, same URL)
|
|
|
224
221
|
flypod update ./dist # same, with an explicit path
|
|
225
222
|
```
|
|
226
223
|
|
|
224
|
+
```
|
|
225
|
+
✓ Updated · version 8f1a0c2e is live
|
|
226
|
+
|
|
227
|
+
https://a3f1c2d4e5b60789.flypod.page
|
|
228
|
+
|
|
229
|
+
undo flypod rollback puts the previous version back
|
|
230
|
+
expires 19 Oct 2026 in 14 days
|
|
231
|
+
keep it flypod login free · removes the expiry
|
|
232
|
+
```
|
|
233
|
+
|
|
227
234
|
Every deploy is a version, identified by the content hash of its files.
|
|
228
235
|
Re-deploying byte-identical content resolves to the **same version id** and adds
|
|
229
236
|
nothing to the history — the CLI just reports that version as live. Old versions
|
|
@@ -278,7 +285,7 @@ loud warning plus the token in normal output, and emits the token on **stderr**
|
|
|
278
285
|
under `-q`. It will never leave you with a live site it can't get back to,
|
|
279
286
|
silently.
|
|
280
287
|
|
|
281
|
-
`--json`
|
|
288
|
+
`--json --verbose` includes `manage_token` for programmatic use, and
|
|
282
289
|
`FLYPOD_SHOW_TOKEN=1` restores the old inline output.
|
|
283
290
|
|
|
284
291
|
## How do I roll back?
|
|
@@ -291,9 +298,22 @@ flypod rollback # previous version becomes live
|
|
|
291
298
|
flypod rollback <id> # a specific version — full id or an unambiguous prefix
|
|
292
299
|
```
|
|
293
300
|
|
|
294
|
-
|
|
295
|
-
|
|
296
|
-
|
|
301
|
+
```
|
|
302
|
+
✓ Rolled back · version 7c0d19e2 is live
|
|
303
|
+
|
|
304
|
+
https://a3f1c2d4e5b60789.flypod.page
|
|
305
|
+
```
|
|
306
|
+
|
|
307
|
+
At a terminal `versions` prints an aligned table with the live version marked:
|
|
308
|
+
|
|
309
|
+
```
|
|
310
|
+
8f1a0c2e44b7d913 18 Jun 2026 14:22 UTC ● live
|
|
311
|
+
7c0d19e2a4b35f18 17 Jun 2026 09:11 UTC
|
|
312
|
+
```
|
|
313
|
+
|
|
314
|
+
Piped, it prints the same list as tab-separated `version_id created_at live`
|
|
315
|
+
rows on stdout, with `created_at` as a readable UTC date. `--json` keeps it as
|
|
316
|
+
epoch milliseconds, so scripts and agents parse the same value they always did.
|
|
297
317
|
`--json` is supported on `update`, `versions`, and `rollback` for stable,
|
|
298
318
|
scriptable output.
|
|
299
319
|
|
|
@@ -311,16 +331,17 @@ npx flypod ./dist --json
|
|
|
311
331
|
"ok": true,
|
|
312
332
|
"url": "https://a3f1c2d4e5b60789.flypod.page",
|
|
313
333
|
"site_id": "a3f1c2d4e5b60789",
|
|
314
|
-
"version_id": "
|
|
334
|
+
"version_id": "8f1a0c2e44b7d913",
|
|
315
335
|
"expires_at": 1782929906088,
|
|
316
|
-
"manage_token": "…",
|
|
317
|
-
"claim_token": "…",
|
|
318
|
-
"source": "dist",
|
|
319
|
-
"files": 12,
|
|
320
|
-
"bytes": 1234567,
|
|
321
|
-
"elapsed_ms": 812,
|
|
322
336
|
"healed": ["spa-fallback"],
|
|
323
|
-
"warnings": []
|
|
337
|
+
"warnings": [],
|
|
338
|
+
"link_saved": true,
|
|
339
|
+
"next": {
|
|
340
|
+
"update": "flypod update",
|
|
341
|
+
"versions": "flypod versions",
|
|
342
|
+
"rollback": "flypod rollback",
|
|
343
|
+
"keep": "flypod login"
|
|
344
|
+
}
|
|
324
345
|
}
|
|
325
346
|
```
|
|
326
347
|
|
|
@@ -339,10 +360,21 @@ For an agent, that pair is a closed loop — deploy, read the receipt, apply the
|
|
|
339
360
|
`fix_recipe`, `flypod update` — without a human in it.
|
|
340
361
|
|
|
341
362
|
`expires_at` is epoch **milliseconds** while the site is temporary, and `null`
|
|
342
|
-
once it's yours.
|
|
343
|
-
`
|
|
344
|
-
|
|
345
|
-
with no flags; when it is `false` the `next` commands carry
|
|
363
|
+
once it's yours. `next` holds the literal commands for what comes after;
|
|
364
|
+
`next.update` is the one that matters, because running `flypod` again makes a
|
|
365
|
+
second site. `link_saved` says whether `flypod update` will work from this
|
|
366
|
+
folder with no flags; when it is `false` the `next` commands carry
|
|
367
|
+
`--site <id>`, and the receipt includes `manage_token`, because nobody else is
|
|
368
|
+
holding it.
|
|
369
|
+
|
|
370
|
+
**The receipt is short on purpose.** It is what an agent acts on, and it
|
|
371
|
+
carries no credentials: a JSON receipt is exactly what gets pasted into a
|
|
372
|
+
chat, a log, or a pull request, and a `manage_token` cannot be rotated.
|
|
373
|
+
`--json --verbose` adds the rest: `manage_token` and `claim_token`, `source`,
|
|
374
|
+
`files`, `bytes`, `elapsed_ms`, `owner_account_id` on an owned deploy, the
|
|
375
|
+
expiry restated as `expires_in_days` and `expires_at_iso`, and a `next_note` in
|
|
376
|
+
prose. Keys that don't apply are omitted rather than emitted
|
|
377
|
+
as `null`.
|
|
346
378
|
|
|
347
379
|
**Every failure is JSON too**, on every verb, so `--json` is safe to parse
|
|
348
380
|
unconditionally:
|
|
@@ -378,7 +410,7 @@ URL=$(npx flypod ./dist --quiet) # stdout: the URL, and nothing else
|
|
|
378
410
|
|
|
379
411
|
`-q` prints no credential. It's the CI and agent mode, which is exactly where a
|
|
380
412
|
secret on stderr ends up in a build log that outlives the site — and a
|
|
381
|
-
`manage_token` can't be rotated. Machines that need it use `--json`. (The single
|
|
413
|
+
`manage_token` can't be rotated. Machines that need it use `--json --verbose`. (The single
|
|
382
414
|
exception is the couldn't-save-the-link case above, where `-q` does emit the
|
|
383
415
|
token on stderr, because otherwise nobody would hold it.)
|
|
384
416
|
|
|
@@ -389,6 +421,75 @@ token in the environment:
|
|
|
389
421
|
FLYPOD_TOKEN=<session-token> npx flypod ./dist --json
|
|
390
422
|
```
|
|
391
423
|
|
|
424
|
+
## How do I deploy from a chat app?
|
|
425
|
+
|
|
426
|
+
flypod is also a remote [MCP](https://modelcontextprotocol.io) server, so an AI
|
|
427
|
+
app with no terminal can publish what it just made. Add this URL as a
|
|
428
|
+
connector, with no sign-in:
|
|
429
|
+
|
|
430
|
+
```
|
|
431
|
+
https://flypod.dev/mcp
|
|
432
|
+
```
|
|
433
|
+
|
|
434
|
+
```sh
|
|
435
|
+
claude mcp add --transport http flypod https://flypod.dev/mcp # Claude Code
|
|
436
|
+
codex mcp add flypod --url https://flypod.dev/mcp # Codex CLI
|
|
437
|
+
```
|
|
438
|
+
|
|
439
|
+
In Claude: Customize → Connectors → Add custom connector. In ChatGPT:
|
|
440
|
+
developer mode → add an MCP server, "No Authentication". Then ask it to
|
|
441
|
+
publish something.
|
|
442
|
+
|
|
443
|
+
| Tool | What it does |
|
|
444
|
+
|------|--------------|
|
|
445
|
+
| `deploy_site` | Publishes files as a new site and returns its URL |
|
|
446
|
+
| `update_site` | Publishes a new version at the same URL |
|
|
447
|
+
| `rollback_site` | Makes an earlier version live again |
|
|
448
|
+
| `get_site` | A site's URL, expiry and version history |
|
|
449
|
+
|
|
450
|
+
`deploy_site` takes `files` (path → text) and optionally `binary_files` (path →
|
|
451
|
+
base64, for small images), up to 200 files and 4 MB. It returns the URL plus a
|
|
452
|
+
`site_id` and `manage_token`, which the other tools need — the app holds them
|
|
453
|
+
for the conversation, since there is no folder on disk to remember them.
|
|
454
|
+
|
|
455
|
+
A site made this way is temporary, like any deploy without an account. The
|
|
456
|
+
result includes a `keep_url`: a page where the person signs in and presses one
|
|
457
|
+
button to keep the site for good, with no terminal involved. Clients that can
|
|
458
|
+
set a header can skip that and make every deploy yours from the start:
|
|
459
|
+
`--header "Authorization: Bearer $FLYPOD_TOKEN"`.
|
|
460
|
+
|
|
461
|
+
Every tool call becomes an ordinary API request inside the server, so the
|
|
462
|
+
connector is held to the same rate limit, upload rules and content screening
|
|
463
|
+
as the CLI.
|
|
464
|
+
|
|
465
|
+
## How are files served?
|
|
466
|
+
|
|
467
|
+
The way a static export expects, with nothing to configure:
|
|
468
|
+
|
|
469
|
+
| Request | Served |
|
|
470
|
+
|---------|--------|
|
|
471
|
+
| `/about.html` | `about.html` |
|
|
472
|
+
| `/about` | `about.html` |
|
|
473
|
+
| `/blog/` | `blog/index.html` |
|
|
474
|
+
| `/blog` | redirect to `/blog/` when the file is `blog/index.html` |
|
|
475
|
+
| a page that does not exist | your `404.html` if you ship one, with a 404 status |
|
|
476
|
+
| any path, on a single-page app | `index.html`, so client-side routing works |
|
|
477
|
+
|
|
478
|
+
- **Caching.** Files whose name carries a build hash (`app.3f9a2c1b.js`,
|
|
479
|
+
`assets/index-BjK3x9aZ.css`, anything under `_next/static/` or `_astro/`)
|
|
480
|
+
are served `immutable` for a year. Everything else revalidates after a
|
|
481
|
+
minute, so a `flypod update` shows up promptly.
|
|
482
|
+
- **Media.** Non-HTML files answer byte-range requests, which is what lets
|
|
483
|
+
video and audio play on Safari and iOS.
|
|
484
|
+
- **Link previews.** A page with no `og:title` or `og:description` gets them
|
|
485
|
+
from its own `<title>` and first paragraph, so a pasted URL unfurls with the
|
|
486
|
+
page's title instead of a bare address. Tags you wrote are never changed.
|
|
487
|
+
`<meta name="flypod" content="none">` turns this and the attribution block
|
|
488
|
+
off.
|
|
489
|
+
- **Dead links.** An address with no site shows a browser a short page saying
|
|
490
|
+
that previews last 14 days and how the owner keeps one.
|
|
491
|
+
- **Read-only.** A site answers `GET` and `HEAD`; anything else gets a `405`.
|
|
492
|
+
|
|
392
493
|
## Deploying Markdown
|
|
393
494
|
|
|
394
495
|
Point flypod at `.md` files and it renders them into a browsable site — no
|
|
@@ -415,13 +516,38 @@ client that asks for Markdown gets the original back from the same URL:
|
|
|
415
516
|
curl -H 'Accept: text/markdown' https://a3f1c2d4e5b60789.flypod.page/guide.html
|
|
416
517
|
```
|
|
417
518
|
|
|
519
|
+
### `llms.txt` on every site
|
|
520
|
+
|
|
521
|
+
An AI agent asks a site for `/llms.txt` to learn what pages it has without
|
|
522
|
+
crawling it. Every flypod site answers:
|
|
523
|
+
|
|
524
|
+
```sh
|
|
525
|
+
curl https://a3f1c2d4e5b60789.flypod.page/llms.txt
|
|
526
|
+
```
|
|
527
|
+
|
|
528
|
+
```
|
|
529
|
+
# Acme
|
|
530
|
+
|
|
531
|
+
## Pages
|
|
532
|
+
|
|
533
|
+
- [Acme](https://a3f1c2d4e5b60789.flypod.page/)
|
|
534
|
+
- [Pricing](https://a3f1c2d4e5b60789.flypod.page/pricing.html)
|
|
535
|
+
- [Docs](https://a3f1c2d4e5b60789.flypod.page/docs/)
|
|
536
|
+
```
|
|
537
|
+
|
|
538
|
+
There is nothing to configure. If your deploy ships its own `llms.txt`, that
|
|
539
|
+
file is served unchanged; otherwise flypod generates one from the site's HTML
|
|
540
|
+
pages and their titles, the first time it is requested. It always describes
|
|
541
|
+
the live version, and it adds nothing to a deploy.
|
|
542
|
+
|
|
418
543
|
## Flags
|
|
419
544
|
|
|
420
545
|
Deploy flags:
|
|
421
546
|
|
|
422
547
|
| Flag | Description |
|
|
423
548
|
|------|-------------|
|
|
424
|
-
| `--json` | Emit
|
|
549
|
+
| `--json` | Emit the result as JSON on stdout (replaces the pretty output) |
|
|
550
|
+
| `--verbose` | More of the same receipt. In a terminal: the rollback and history commands, plus the site id, version id and source folder. With `--json`: also tokens, counts, timing. Also on `flypod update` |
|
|
425
551
|
| `-q`, `--quiet` | Print only the URL on stdout, and nothing else |
|
|
426
552
|
| `--comments` | Enable comments on the new site (requires being signed in) |
|
|
427
553
|
| `--mode <mode>` | With `--comments`: `anonymous` (default), `passcode`, or `approved` |
|
|
@@ -639,6 +765,9 @@ folder found under `cwd` that contains an `index.html`. Throws if none match.
|
|
|
639
765
|
|
|
640
766
|
## HTTP API
|
|
641
767
|
|
|
768
|
+
(For AI apps there is also an MCP endpoint at `https://flypod.dev/mcp` — see
|
|
769
|
+
[How do I deploy from a chat app?](#how-do-i-deploy-from-a-chat-app))
|
|
770
|
+
|
|
642
771
|
The CLI wraps these. Reach for raw HTTP only when scripting against the API
|
|
643
772
|
directly. Management calls authorize with the site's `manage_token`, or with an
|
|
644
773
|
account session for owned sites.
|