flypod 0.11.2 → 0.11.3
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 +9 -2
- package/dist/bin/deploy.js +1 -1
- package/dist/{cli-c6hpb7tq.js → cli-zc5d42zg.js} +7 -0
- package/dist/src/cli.js +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -387,7 +387,11 @@ Branch on `code` — it is stable; `error` is prose and may change; `fix`, when
|
|
|
387
387
|
present, is the literal next step. The codes: `no_build_dir`, `no_files`,
|
|
388
388
|
`no_site`, `not_signed_in`, `unauthorized`, `token_rejected`, `site_gone`,
|
|
389
389
|
`invalid_upload`, `too_large`, `blocked`, `challenge_required`, `rate_limited`,
|
|
390
|
-
`server_error`, `network`, `usage`, `unknown_flag`,
|
|
390
|
+
`server_error`, `network`, `usage`, `unknown_flag`, `unknown_command` (a
|
|
391
|
+
`flypod comments` verb that does not exist), `no_such_version` (nothing to roll
|
|
392
|
+
back to), `no_token` (`flypod token` on a site this machine holds no manage
|
|
393
|
+
token for), `already_claimed`, `not_found`, `bad_request` (any other 4xx),
|
|
394
|
+
`unexpected`, and the login codes below.
|
|
391
395
|
The [exit code](#exit-codes) follows the code, never the verb.
|
|
392
396
|
|
|
393
397
|
A credential that is sent but not accepted (an expired `FLYPOD_TOKEN`, say)
|
|
@@ -400,7 +404,10 @@ anonymous 14-day site.
|
|
|
400
404
|
of waiting. Hand the URL and code to the user; once they confirm, finish with
|
|
401
405
|
`flypod login --device-code <device_code>` — that polls once and either saves
|
|
402
406
|
the session (`{"ok": true, "logged_in": true}`) or reports
|
|
403
|
-
`authorization_pending` (exit 4) to try again.
|
|
407
|
+
`authorization_pending` (exit 4) to try again. The flow ends for good with
|
|
408
|
+
`login_denied` (exit 3, the user said no) or `login_expired` (exit 1, start
|
|
409
|
+
again); an interactive `flypod login` that gives up waiting reports
|
|
410
|
+
`login_timeout` (exit 4).
|
|
404
411
|
|
|
405
412
|
Or capture just the URL:
|
|
406
413
|
|
package/dist/bin/deploy.js
CHANGED
|
@@ -331,6 +331,13 @@ step when there is one. Codes you will meet: \`no_build_dir\`, \`no_files\`,
|
|
|
331
331
|
\`invalid_upload\`, \`too_large\`, \`blocked\`, \`challenge_required\`,
|
|
332
332
|
\`rate_limited\`, \`server_error\`, \`network\`, \`unknown_flag\`, \`usage\`.
|
|
333
333
|
|
|
334
|
+
Rarer ones: \`unknown_command\` (a \`flypod comments\` verb that does not exist),
|
|
335
|
+
\`no_such_version\` (nothing to roll back to), \`no_token\` (\`flypod token\` on a
|
|
336
|
+
site this machine holds no manage token for), \`already_claimed\`, \`not_found\`,
|
|
337
|
+
\`bad_request\` (any other 4xx), \`unexpected\`, and from the login flow
|
|
338
|
+
\`login_denied\` (exit 3), \`login_expired\` (exit 1, start again) and
|
|
339
|
+
\`login_timeout\` (exit 4).
|
|
340
|
+
|
|
334
341
|
A \`FLYPOD_TOKEN\` the server does not accept fails the deploy with
|
|
335
342
|
\`token_rejected\` (exit 3). It never falls back to an anonymous deploy, so an
|
|
336
343
|
exit 0 with a token set always means the site is owned.
|
package/dist/src/cli.js
CHANGED
package/package.json
CHANGED