@builtbyfriends/bwf 0.0.0-stage → 1.9.1
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/AGENTS_TEMPLATE.md +4 -0
- package/LICENSE +22 -0
- package/README.md +48 -2
- package/dist/account-cmd-Cj0I2_bJ.mjs +45 -0
- package/dist/agents-BLiMq9E1.mjs +113 -0
- package/dist/application-analysis-C9Ck2Yeg.mjs +1498 -0
- package/dist/application-routing-DbR-W5lG.mjs +25 -0
- package/dist/atomic-write-DA6eD1Kp.mjs +17 -0
- package/dist/auth-BKsUmWbT.d.mts +77 -0
- package/dist/auth-DkvoW5hB.mjs +33 -0
- package/dist/auth-aKyIWkdS.mjs +1 -0
- package/dist/auth-client-6-Ft9i9T.d.mts +5 -0
- package/dist/auth-client-DwCdwKbw.mjs +5 -0
- package/dist/auth-client-react-CJdeErvM.mjs +5 -0
- package/dist/auth-client-react-DvQLe5Zb.d.mts +5 -0
- package/dist/auth-link-D-DddkCQ.mjs +26 -0
- package/dist/auth-migrations-DDeifS3v.mjs +206 -0
- package/dist/auth-router-tWzIwf8f.mjs +66 -0
- package/dist/auth-xnkmpZUl.mjs +311 -0
- package/dist/base64-ikl9yBy3.mjs +15 -0
- package/dist/better-auth-shared-Br6TNaYJ.mjs +473 -0
- package/dist/better-auth-shared-CsBNvPOU.d.mts +56 -0
- package/dist/build-cmd-BnZezraT.mjs +153 -0
- package/dist/build-output-dir-Clj_unKN.mjs +402 -0
- package/dist/cancel-deploy-DKAj5U1Z.mjs +57 -0
- package/dist/cf-access-Bhz9wX6p.mjs +131 -0
- package/dist/cf-access-CUP5L08W.mjs +67 -0
- package/dist/cf-build-output-DA6uJomQ.mjs +1 -0
- package/dist/cf-build-output-DNQTwMNU.mjs +438 -0
- package/dist/cf-command-values-2kOtxMo1.mjs +26 -0
- package/dist/cf-config-migrate-COOCi4Ge.mjs +330 -0
- package/dist/cf-worker-settings-CIh4t_yG.mjs +41 -0
- package/dist/cli/cli.d.mts +1 -0
- package/dist/cli/cli.mjs +88 -0
- package/dist/cli/cloudflare-operation-process.d.mts +1 -0
- package/dist/cli/cloudflare-operation-process.mjs +1284 -0
- package/dist/cli/env-schema-probe.d.mts +43 -0
- package/dist/cli/env-schema-probe.mjs +165 -0
- package/dist/cli-main-HeXRQml6.mjs +1846 -0
- package/dist/client-D3D5RM5h.mjs +940 -0
- package/dist/client-VF2Nzc7Z.mjs +1 -0
- package/dist/cloudflare-auth-jb-1e43r.mjs +152 -0
- package/dist/cloudflare-cmd-B62t8Fm-.mjs +59 -0
- package/dist/cloudflare-config-i8yanry0.mjs +186 -0
- package/dist/cloudflare-connect-x7IsYghw.mjs +55 -0
- package/dist/cloudflare-operations-BeK7bhnP.mjs +627 -0
- package/dist/cloudflare-operations-C3Uu0Emj.mjs +1 -0
- package/dist/cloudflare-process-Cc6oiJqk.mjs +309 -0
- package/dist/cloudflare-user-output-CqONaAbP.mjs +19 -0
- package/dist/collect-8i0wU63d.mjs +1 -0
- package/dist/collect-C6Blu9yw.mjs +48 -0
- package/dist/config-CN_RFRkS.mjs +86 -0
- package/dist/config-D5G-Tx6o.mjs +1 -0
- package/dist/config-DOaFIK3w.mjs +88 -0
- package/dist/config-entry.d.mts +202 -0
- package/dist/config-entry.mjs +6 -0
- package/dist/config-tNx0HlFv.mjs +516 -0
- package/dist/connect-hLPNppu3.mjs +84 -0
- package/dist/create-project-B35ux-LA.mjs +126 -0
- package/dist/create-project-tJ1KwNss.mjs +1 -0
- package/dist/database-provider-DkZo4VwN.mjs +5 -0
- package/dist/database-provider.d.mts +25 -0
- package/dist/database-provider.mjs +1 -0
- package/dist/db-BH_md90k.mjs +1735 -0
- package/dist/delete-BSKI7V23.mjs +65 -0
- package/dist/deploy-C8KHBNsh.mjs +6512 -0
- package/dist/deploy-DCZBr7Ey.mjs +2 -0
- package/dist/deploy.d.mts +31 -0
- package/dist/deploy.mjs +118 -0
- package/dist/dev-inbox-I0nqTCdf.mjs +216 -0
- package/dist/discover-DJPmQcL5.mjs +36 -0
- package/dist/discover-EVuydEoM.mjs +1 -0
- package/dist/dist-B6eN80gc.mjs +1612 -0
- package/dist/dist-Cp4b1_T9.mjs +1 -0
- package/dist/dist-DMYe8CZJ.mjs +48 -0
- package/dist/dist-STQXl8ck.mjs +1878 -0
- package/dist/domain-C4ZhEiFG.mjs +149 -0
- package/dist/dotenv-4NdUCXbB.mjs +156 -0
- package/dist/drizzle-DqVFXtlc.mjs +306 -0
- package/dist/drizzle-Ds5P0n-S.mjs +1 -0
- package/dist/edge.d.mts +2 -0
- package/dist/edge.mjs +1 -0
- package/dist/email-B3TWga7x.mjs +742 -0
- package/dist/email-C_ATvNIG.mjs +2865 -0
- package/dist/email-cloudflare-DuAc9zny.mjs +854 -0
- package/dist/email-protocol-CZ0bAkI8.mjs +81 -0
- package/dist/env-CTAo8ifZ.mjs +73 -0
- package/dist/env-DUyTzroe.mjs +88 -0
- package/dist/env-Dl4Wggec.mjs +71 -0
- package/dist/env-helpers-BX0APszT.mjs +135 -0
- package/dist/env-helpers-U56xuFgL.d.mts +20 -0
- package/dist/env-mask-BsHxq3R8.mjs +46 -0
- package/dist/env-public-Cw_xPi1D.d.mts +119 -0
- package/dist/env-raw-Bo6TtrHU.mjs +41 -0
- package/dist/env-types-Bg-dTh8u.mjs +56 -0
- package/dist/env-validation-BufZConV.mjs +488 -0
- package/dist/env-validation-DPqDo4DU.mjs +1 -0
- package/dist/fetch-CBgyyhzm.d.mts +87 -0
- package/dist/fetch-error-DmlRM6e4.mjs +264 -0
- package/dist/fetch-stream-2GUN3YN1.mjs +102 -0
- package/dist/fetch-stream-bUXynOyZ.d.mts +32 -0
- package/dist/fetch-tpPiSK10.mjs +25 -0
- package/dist/gen-dc13IRXh.mjs +509 -0
- package/dist/gen-kQqhFyOP.mjs +1 -0
- package/dist/generate-BgtlYpKg.mjs +1 -0
- package/dist/generate-Da9mWKzU.mjs +80 -0
- package/dist/generated-wrangler-config-CoDaaFsA.mjs +17 -0
- package/dist/git-metadata-Cukp5kV5.mjs +82 -0
- package/dist/github-cmd-DT5Onu6E.mjs +690 -0
- package/dist/handler-CJ7DiiRF.mjs +161 -0
- package/dist/handler-CVsIfRv7.d.mts +279 -0
- package/dist/help-Bpv6Qeqn.mjs +1946 -0
- package/dist/help-CfZ4Bsw5.mjs +1 -0
- package/dist/inbound-CqubE-9T.d.mts +311 -0
- package/dist/inbound-lHugZPuK.mjs +509 -0
- package/dist/index.d.mts +64 -0
- package/dist/index.mjs +4163 -0
- package/dist/info-CLQoCenb.mjs +109 -0
- package/dist/init-DRUR0j8C.mjs +2486 -0
- package/dist/limits-CMmYT2l8.d.mts +16 -0
- package/dist/limits-D27Lp6FP.mjs +46 -0
- package/dist/link-DinwJnon.mjs +52 -0
- package/dist/list-B84t4BhW.mjs +130 -0
- package/dist/live-Dui0-aj_.d.mts +105 -0
- package/dist/live-saC8barp.mjs +410 -0
- package/dist/load-user-env-g0ahkZcj.mjs +34 -0
- package/dist/local-d1-C3EeOV7-.mjs +103 -0
- package/dist/log-JDnPc0cF.mjs +23 -0
- package/dist/login-Bl5lH8nH.mjs +87 -0
- package/dist/login-DoI7AsbY.mjs +1 -0
- package/dist/logs-CaT2N2f7.mjs +129 -0
- package/dist/migrate-CbGscX-V.mjs +125 -0
- package/dist/migrate-Ce3JKLVs.mjs +1 -0
- package/dist/migration-handler-22qiuWPq.mjs +469 -0
- package/dist/migration-handler-Bb2BJh6g.d.mts +38 -0
- package/dist/mime-BMUN_QKG.mjs +1004 -0
- package/dist/mysql-migration-sql-CNuBSqdx.mjs +239 -0
- package/dist/neon-CJzQSycr.mjs +52 -0
- package/dist/node-tfv-3v0V.mjs +64 -0
- package/dist/operator-ai-logging-Ay7M4KWw.mjs +121 -0
- package/dist/operator-args-BFg32YyY.mjs +722 -0
- package/dist/operator-auth-DdYZYEkO.mjs +47 -0
- package/dist/operator-client-DBujdELO.mjs +82 -0
- package/dist/operator-cmd-C73WWJBl.mjs +443 -0
- package/dist/operator-cmd-CdZytuAF.mjs +1 -0
- package/dist/output-Bb34lF0w.mjs +173 -0
- package/dist/output-CVolXKC1.mjs +1 -0
- package/dist/package-DO4d3Qz5.mjs +1444 -0
- package/dist/package-json-DvS6IFRv.mjs +43 -0
- package/dist/pg-DoyPxa_X.mjs +15 -0
- package/dist/picocolors-D1NxSLw-.mjs +71 -0
- package/dist/plan-BHNt1QhK.mjs +1 -0
- package/dist/plan-DX4_-OM5.mjs +58 -0
- package/dist/platform-args-NI_vfWvD.mjs +538 -0
- package/dist/platform-args-ZC1-A1N9.mjs +1 -0
- package/dist/platform-auth-config-d-lY5-aY.mjs +371 -0
- package/dist/platform-auth-protection-Dhw7lUCk.mjs +231 -0
- package/dist/platform-auth-recovery-DaCc0tlx.mjs +309 -0
- package/dist/platform-cmd-5Ry-C9im.mjs +193 -0
- package/dist/platform-cmd-5oZq91lI.mjs +1 -0
- package/dist/platform-discovery-Bxg9aZXU.mjs +40 -0
- package/dist/platform-domain-DLVdGvGG.mjs +256 -0
- package/dist/platform-lifecycle-CUgjipXO.mjs +1 -0
- package/dist/platform-lifecycle-fRt5VMls.mjs +8928 -0
- package/dist/platform-management-5hEsRfR2.mjs +1 -0
- package/dist/platform-management-Djh1hzLP.mjs +1607 -0
- package/dist/platform-plans-config-CkbUKFpm.mjs +447 -0
- package/dist/platform-recovery-Cghx7FCR.mjs +96 -0
- package/dist/platform-registry-x1m9HBxf.mjs +450 -0
- package/dist/platform-runtime-logs-kkoiYFpF.mjs +72 -0
- package/dist/platform-setup-SfwCwnZg.mjs +306 -0
- package/dist/prepare-B9mB47T5.mjs +84 -0
- package/dist/prepare-DNIq07so.mjs +13 -0
- package/dist/prepare-LHkyJqxi.mjs +1 -0
- package/dist/project-CC7eN00D.mjs +141 -0
- package/dist/project-DcSd4BeI.mjs +1 -0
- package/dist/project-cmd-DTF19-fC.mjs +109 -0
- package/dist/project-paths-iXHKRTTQ.mjs +159 -0
- package/dist/project-slug-BUy0lmyR.mjs +1 -0
- package/dist/project-slug-CO6ci9XG.mjs +7 -0
- package/dist/project-team-CvdLhDF2.mjs +129 -0
- package/dist/project-token-CwZdUEGu.mjs +70 -0
- package/dist/project-tsconfig-P9X952KG.mjs +98 -0
- package/dist/project-zero-trust-CKDoPdN1.mjs +64 -0
- package/dist/providers-Cd3c7wi0.mjs +64 -0
- package/dist/providers-Df69hb_X.d.mts +5 -0
- package/dist/provision-DGlFJ3T9.mjs +1 -0
- package/dist/provision-mYVLuQiy.mjs +1814 -0
- package/dist/queues-Bc3FsBQT.d.mts +5 -0
- package/dist/r2-conditions-DSLmkiR5.mjs +60 -0
- package/dist/requests-DNhfyF3l.mjs +52 -0
- package/dist/resolve-project-BCsAMDRA.mjs +47 -0
- package/dist/resolve-project-DhU9_lIo.mjs +1 -0
- package/dist/resource-name-DlJ9QXzg.mjs +10 -0
- package/dist/response-HmNjB30w.mjs +29 -0
- package/dist/rollback-BvCHol52.mjs +150 -0
- package/dist/rolldown-runtime-uD8oG6U2.mjs +24 -0
- package/dist/route-types-CRWhr93D.mjs +592 -0
- package/dist/route-url-BIDZT78M.mjs +58 -0
- package/dist/route-url-Bla3Upsy.d.mts +42 -0
- package/dist/routes-stub.d.mts +24 -0
- package/dist/routes-stub.mjs +1 -0
- package/dist/routing-assets-CSheDWWM.mjs +54 -0
- package/dist/rpc-DcByS_q0.d.mts +39 -0
- package/dist/rpc-DtxIN9Tv.mjs +19 -0
- package/dist/runner-CPerdjIl.mjs +163 -0
- package/dist/runner-CUNtS5x7.mjs +1 -0
- package/dist/runner-mysql-7aA5hGoM.mjs +145 -0
- package/dist/runner-mysql-DrMKw203.mjs +1 -0
- package/dist/runner-pg-2pjltt0t.mjs +1 -0
- package/dist/runner-pg-mYc75KfH.mjs +61 -0
- package/dist/runtime/ai.d.mts +50 -0
- package/dist/runtime/ai.mjs +455 -0
- package/dist/runtime/auth-client-react.d.mts +2 -0
- package/dist/runtime/auth-client-react.mjs +1 -0
- package/dist/runtime/auth-client.d.mts +2 -0
- package/dist/runtime/auth-client.mjs +1 -0
- package/dist/runtime/auth.d.mts +2 -0
- package/dist/runtime/auth.mjs +1 -0
- package/dist/runtime/better-auth-mysql.d.mts +5 -0
- package/dist/runtime/better-auth-mysql.mjs +21 -0
- package/dist/runtime/better-auth-pg.d.mts +5 -0
- package/dist/runtime/better-auth-pg.mjs +21 -0
- package/dist/runtime/better-auth.d.mts +6 -0
- package/dist/runtime/better-auth.mjs +22 -0
- package/dist/runtime/client-react.d.mts +5 -0
- package/dist/runtime/client-react.mjs +5 -0
- package/dist/runtime/client.d.mts +5 -0
- package/dist/runtime/client.mjs +5 -0
- package/dist/runtime/db-mysql.d.mts +2 -0
- package/dist/runtime/db-mysql.mjs +1 -0
- package/dist/runtime/db-pg.d.mts +2 -0
- package/dist/runtime/db-pg.mjs +1 -0
- package/dist/runtime/db.d.mts +17 -0
- package/dist/runtime/db.mjs +36 -0
- package/dist/runtime/drizzle-arktype.d.mts +1 -0
- package/dist/runtime/drizzle-arktype.mjs +2 -0
- package/dist/runtime/drizzle-valibot.d.mts +1 -0
- package/dist/runtime/drizzle-valibot.mjs +2 -0
- package/dist/runtime/drizzle-zod.d.mts +1 -0
- package/dist/runtime/drizzle-zod.mjs +2 -0
- package/dist/runtime/durable.d.mts +64 -0
- package/dist/runtime/durable.mjs +165 -0
- package/dist/runtime/email/testing.d.mts +108 -0
- package/dist/runtime/email/testing.mjs +268 -0
- package/dist/runtime/email-protocol.d.mts +25 -0
- package/dist/runtime/email-protocol.mjs +1 -0
- package/dist/runtime/email.d.mts +26 -0
- package/dist/runtime/email.mjs +524 -0
- package/dist/runtime/env-public-client.d.mts +19 -0
- package/dist/runtime/env-public-client.mjs +55 -0
- package/dist/runtime/env-public.d.mts +4 -0
- package/dist/runtime/env-public.mjs +277 -0
- package/dist/runtime/env.d.mts +12 -0
- package/dist/runtime/env.mjs +1 -0
- package/dist/runtime/fetch-server.d.mts +6 -0
- package/dist/runtime/fetch-server.mjs +29 -0
- package/dist/runtime/fetch-stream.d.mts +3 -0
- package/dist/runtime/fetch-stream.mjs +3 -0
- package/dist/runtime/fetch.d.mts +2 -0
- package/dist/runtime/fetch.mjs +3 -0
- package/dist/runtime/handler.d.mts +3 -0
- package/dist/runtime/handler.mjs +1 -0
- package/dist/runtime/kv.d.mts +45 -0
- package/dist/runtime/kv.mjs +103 -0
- package/dist/runtime/limits.d.mts +2 -0
- package/dist/runtime/limits.mjs +1 -0
- package/dist/runtime/live-client.d.mts +40 -0
- package/dist/runtime/live-client.mjs +282 -0
- package/dist/runtime/live-server.d.mts +11 -0
- package/dist/runtime/live-server.mjs +419 -0
- package/dist/runtime/live.d.mts +3 -0
- package/dist/runtime/live.mjs +1 -0
- package/dist/runtime/log.d.mts +24 -0
- package/dist/runtime/log.mjs +57 -0
- package/dist/runtime/migration-handler-mysql.d.mts +2 -0
- package/dist/runtime/migration-handler-mysql.mjs +111 -0
- package/dist/runtime/migration-handler-pg.d.mts +2 -0
- package/dist/runtime/migration-handler-pg.mjs +94 -0
- package/dist/runtime/migration-handler.d.mts +2 -0
- package/dist/runtime/migration-handler.mjs +1 -0
- package/dist/runtime/procedure.d.mts +27 -0
- package/dist/runtime/procedure.mjs +36 -0
- package/dist/runtime/procedures.d.mts +24 -0
- package/dist/runtime/procedures.mjs +56 -0
- package/dist/runtime/queues.d.mts +2 -0
- package/dist/runtime/queues.mjs +8 -0
- package/dist/runtime/remote/binding-handler.d.mts +11 -0
- package/dist/runtime/remote/binding-handler.mjs +227 -0
- package/dist/runtime/remote/index.d.mts +12 -0
- package/dist/runtime/remote/index.mjs +467 -0
- package/dist/runtime/response.d.mts +11 -0
- package/dist/runtime/response.mjs +1 -0
- package/dist/runtime/route-url.d.mts +2 -0
- package/dist/runtime/route-url.mjs +1 -0
- package/dist/runtime/routing.d.mts +53 -0
- package/dist/runtime/routing.mjs +425 -0
- package/dist/runtime/rpc-react.d.mts +16 -0
- package/dist/runtime/rpc-react.mjs +50 -0
- package/dist/runtime/rpc.d.mts +2 -0
- package/dist/runtime/rpc.mjs +1 -0
- package/dist/runtime/sandbox-container.d.mts +3 -0
- package/dist/runtime/sandbox-container.mjs +1 -0
- package/dist/runtime/sandbox.d.mts +5 -0
- package/dist/runtime/sandbox.mjs +196 -0
- package/dist/runtime/schema-d1.d.mts +1 -0
- package/dist/runtime/schema-d1.mjs +2 -0
- package/dist/runtime/schema-mysql.d.mts +1 -0
- package/dist/runtime/schema-mysql.mjs +2 -0
- package/dist/runtime/schema-pg.d.mts +1 -0
- package/dist/runtime/schema-pg.mjs +2 -0
- package/dist/runtime/seed.d.mts +34 -0
- package/dist/runtime/seed.mjs +5 -0
- package/dist/runtime/sse-client.d.mts +31 -0
- package/dist/runtime/sse-client.mjs +42 -0
- package/dist/runtime/sse.d.mts +32 -0
- package/dist/runtime/sse.mjs +1 -0
- package/dist/runtime/storage.d.mts +4 -0
- package/dist/runtime/storage.mjs +13 -0
- package/dist/runtime/validator.d.mts +2 -0
- package/dist/runtime/validator.mjs +1 -0
- package/dist/runtime/ws-server.d.mts +26 -0
- package/dist/runtime/ws-server.mjs +297 -0
- package/dist/runtime/ws.d.mts +2 -0
- package/dist/runtime/ws.mjs +108 -0
- package/dist/sandbox-CWDjoEG2.d.mts +50 -0
- package/dist/sandbox-container-BqamdFCx.d.mts +73 -0
- package/dist/sandbox-container-d1AHLpgn.mjs +291 -0
- package/dist/secret-DCF9RXTc.mjs +146 -0
- package/dist/skills-Dr3AjuBF.mjs +63 -0
- package/dist/sqlite-validation-CLJXXN93.mjs +24 -0
- package/dist/sse-CxR30yMF.mjs +174 -0
- package/dist/standard-schema-CuDawHOC.d.mts +40 -0
- package/dist/static-asset-marker-mWMX2dLa.mjs +38 -0
- package/dist/subcommand-prompt-B9yUo--u.mjs +370 -0
- package/dist/terminal-log-text-DNsWJREL.mjs +31 -0
- package/dist/types-D7-4tBu7.d.mts +1 -0
- package/dist/untrusted-env-lL7RkYiC.mjs +50 -0
- package/dist/validate-B-zsjhiz.mjs +162 -0
- package/dist/validate-DbqGdPPY.mjs +1 -0
- package/dist/validator-8-NZs2Xr.mjs +168 -0
- package/dist/version-metadata-DsSoNsKJ.mjs +23 -0
- package/dist/wrangler-DU784Dkf.mjs +1452 -0
- package/dist/wrangler-Rr9_76DQ.mjs +1 -0
- package/dist/ws-Q_osq9VK.d.mts +137 -0
- package/dist/yarn-pnp-DgWbE7z5.mjs +91 -0
- package/docs/guide/ai.md +273 -0
- package/docs/guide/app-types.md +101 -0
- package/docs/guide/auth.md +255 -0
- package/docs/guide/database/d1.md +86 -0
- package/docs/guide/database/mysql.md +72 -0
- package/docs/guide/database/postgresql.md +94 -0
- package/docs/guide/database.md +454 -0
- package/docs/guide/deployment.md +124 -0
- package/docs/guide/durable-state.md +192 -0
- package/docs/guide/edge/headers.md +47 -0
- package/docs/guide/edge/redirects.md +85 -0
- package/docs/guide/edge/rewrites.md +119 -0
- package/docs/guide/edge/static-assets.md +94 -0
- package/docs/guide/email/domains.md +119 -0
- package/docs/guide/email/receiving.md +142 -0
- package/docs/guide/email/sending.md +262 -0
- package/docs/guide/email.md +23 -0
- package/docs/guide/env-vars.md +115 -0
- package/docs/guide/index.md +37 -0
- package/docs/guide/jobs.md +80 -0
- package/docs/guide/kv.md +100 -0
- package/docs/guide/live.md +181 -0
- package/docs/guide/platform/administration/access.md +165 -0
- package/docs/guide/platform/administration/connected-apps.md +84 -0
- package/docs/guide/platform/administration/email.md +169 -0
- package/docs/guide/platform/administration/operations.md +100 -0
- package/docs/guide/platform/administration/plans.md +156 -0
- package/docs/guide/platform/administration/projects.md +74 -0
- package/docs/guide/platform/administration/zero-trust.md +205 -0
- package/docs/guide/platform/development/local.md +122 -0
- package/docs/guide/platform/development/runtime.md +115 -0
- package/docs/guide/platform/development/schema-ci.md +44 -0
- package/docs/guide/platform/installation/ci.md +62 -0
- package/docs/guide/platform/installation/credentials.md +140 -0
- package/docs/guide/platform/installation/domains.md +120 -0
- package/docs/guide/platform/installation/first-deployment.md +95 -0
- package/docs/guide/platform/installation/maintenance.md +250 -0
- package/docs/guide/platform/installation/prerequisites.md +176 -0
- package/docs/guide/platform/installation/setup.md +300 -0
- package/docs/guide/platform/installation/uninstall.md +110 -0
- package/docs/guide/platform-administration.md +19 -0
- package/docs/guide/platform-development.md +16 -0
- package/docs/guide/procedures.md +48 -0
- package/docs/guide/project-collaboration.md +99 -0
- package/docs/guide/queues.md +149 -0
- package/docs/guide/quickstart.md +129 -0
- package/docs/guide/remote-dev.md +67 -0
- package/docs/guide/sandboxes.md +134 -0
- package/docs/guide/self-hosted-platform.md +45 -0
- package/docs/guide/server-routing.md +283 -0
- package/docs/guide/sse.md +174 -0
- package/docs/guide/storage.md +82 -0
- package/docs/guide/testing.md +64 -0
- package/docs/guide/type-safety.md +270 -0
- package/docs/guide/typed-fetch.md +98 -0
- package/docs/guide/websockets.md +230 -0
- package/docs/index.md +102 -0
- package/docs/integrations/agents.md +38 -0
- package/docs/integrations/cloudflare.md +241 -0
- package/docs/integrations/hono.md +127 -0
- package/docs/reference/api/auth.md +195 -0
- package/docs/reference/api/client.md +90 -0
- package/docs/reference/api/database.md +118 -0
- package/docs/reference/api/deploy.md +63 -0
- package/docs/reference/api/durable.md +47 -0
- package/docs/reference/api/env.md +51 -0
- package/docs/reference/api/handlers.md +189 -0
- package/docs/reference/api/plugin.md +40 -0
- package/docs/reference/api/resources.md +116 -0
- package/docs/reference/api/rewrites.md +111 -0
- package/docs/reference/api/types.md +126 -0
- package/docs/reference/api.md +71 -0
- package/docs/reference/cli/auth.md +87 -0
- package/docs/reference/cli/database.md +159 -0
- package/docs/reference/cli/deploy.md +117 -0
- package/docs/reference/cli/domains.md +42 -0
- package/docs/reference/cli/email.md +145 -0
- package/docs/reference/cli/generate.md +113 -0
- package/docs/reference/cli/github.md +181 -0
- package/docs/reference/cli/platform-config.md +93 -0
- package/docs/reference/cli/platform-email.md +81 -0
- package/docs/reference/cli/platform-installation.md +166 -0
- package/docs/reference/cli/platform-operations.md +90 -0
- package/docs/reference/cli/platform-users.md +159 -0
- package/docs/reference/cli/platform-zero-trust.md +60 -0
- package/docs/reference/cli/platform.md +78 -0
- package/docs/reference/cli/project.md +208 -0
- package/docs/reference/cli/secrets.md +79 -0
- package/docs/reference/cli/setup.md +88 -0
- package/docs/reference/cli.md +115 -0
- package/docs/reference/config.md +478 -0
- package/docs/reference/resource-inference.md +72 -0
- package/docs/reference/structure.md +138 -0
- package/package.json +389 -3
- package/sandbox.Dockerfile +4 -0
- package/schema.json +353 -0
- package/skills/bwf/SKILL.md +100 -0
- package/skills/migrate-vite-cloudflare-to-bwf/SKILL.md +53 -0
- package/templates/assets/bwf.svg +5 -0
- package/templates/assets/icons.svg +49 -0
- package/templates/assets/react.svg +1 -0
- package/templates/assets/stack.svg +35 -0
|
@@ -0,0 +1,145 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: 'Inspect email usage and choose the recipients a project is allowed to send to.'
|
|
3
|
+
outline: deep
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# Email {#email}
|
|
7
|
+
|
|
8
|
+
Inspect email usage and manage the recipients a project is allowed to send to. See [Email](../../guide/email.md) for the runtime API.
|
|
9
|
+
|
|
10
|
+
Project resolution for email commands follows the same order as deploy (`--project`, `BWF_PROJECT`, linked project). `bwf email setup` and `bwf email status --platform cloudflare` are the exception: they act on your own Cloudflare account through your Cloudflare sign-in (`bwf cloudflare login`) and need no bwf project.
|
|
11
|
+
|
|
12
|
+
## `bwf email usage` {#nosam-email-usage}
|
|
13
|
+
|
|
14
|
+
```
|
|
15
|
+
bwf email usage [--project <name>]
|
|
16
|
+
```
|
|
17
|
+
|
|
18
|
+
Show the current month's recipient attempts and inbound receipts, the monthly attempt limit, and how much of it is left. Reserved submissions count toward the limit; started attempts remain charged even if delivery fails or its outcome is unknown. A suspended project is flagged in the output.
|
|
19
|
+
|
|
20
|
+
## `bwf email logs` {#nosam-email-logs}
|
|
21
|
+
|
|
22
|
+
```
|
|
23
|
+
bwf email logs [--limit <n>] [--project <name>]
|
|
24
|
+
```
|
|
25
|
+
|
|
26
|
+
Show recent email operation metadata retained for 30 days: timestamp, direction, operation ID, recipient, and state. `--limit` accepts 1–100. Subjects, bodies, and attachments are not stored. Provider acceptance does not confirm mailbox delivery; inspect unknown outcomes before retrying.
|
|
27
|
+
|
|
28
|
+
## `bwf email destinations` {#nosam-email-destinations}
|
|
29
|
+
|
|
30
|
+
```
|
|
31
|
+
bwf email destinations [--project <name>]
|
|
32
|
+
```
|
|
33
|
+
|
|
34
|
+
List the project's recipient addresses and their state (`verified`, `pending`, or `failed`). Outbound mail is only delivered to verified addresses.
|
|
35
|
+
|
|
36
|
+
## `bwf email allow` {#nosam-email-allow}
|
|
37
|
+
|
|
38
|
+
```
|
|
39
|
+
bwf email allow <address> [--project <name>]
|
|
40
|
+
```
|
|
41
|
+
|
|
42
|
+
Add one recipient to the project's destination list. Cloudflare emails that address a verification link — the recipient clicks it, with no bwf or Cloudflare account required. Then run `bwf email destinations`: the listing is what records the click, and until it has, a send to that address returns `UNVERIFIED_DESTINATION` for that recipient. If the link did not arrive or has expired, run `bwf email allow <address>` again while the address is still pending — the CLI re-sends the link, or tells you how to get a fresh one.
|
|
43
|
+
|
|
44
|
+
The project owner's email is added automatically when the project is created, so it skips this step but not the verification: unless Cloudflare already had it verified for an earlier project of yours, click the link it mailed and run `bwf email destinations`; until then a send to yourself returns `UNVERIFIED_DESTINATION` for that recipient.
|
|
45
|
+
|
|
46
|
+
## `bwf email disallow` {#nosam-email-disallow}
|
|
47
|
+
|
|
48
|
+
```
|
|
49
|
+
bwf email disallow <address> [--project <name>]
|
|
50
|
+
```
|
|
51
|
+
|
|
52
|
+
Remove one recipient from the project's destination list. New sends to that address are refused immediately; previously admitted attempts may finish. No deploy is involved.
|
|
53
|
+
|
|
54
|
+
## `bwf email alias` {#nosam-email-alias}
|
|
55
|
+
|
|
56
|
+
```
|
|
57
|
+
bwf email alias [--project <name>]
|
|
58
|
+
bwf email alias <name> [--yes] [--project <name>]
|
|
59
|
+
```
|
|
60
|
+
|
|
61
|
+
With no name, show the project's address on the platform's shared mail domain and whether inbound mail reaches it.
|
|
62
|
+
|
|
63
|
+
As the project owner, run `bwf email alias acme` to send and receive at `acme@<mail domain>` and `acme+<tag>@<mail domain>`. Choose an available name that follows the project slug rules. Names of five characters or fewer require a plan that allows short names.
|
|
64
|
+
|
|
65
|
+
An alias is permanent and reserved until the project is deleted. The original slug address keeps working. The CLI asks for confirmation; use `--yes` in scripts and CI.
|
|
66
|
+
|
|
67
|
+
Before sharing the alias, redeploy with the current bwf version so handlers receive the expected `message.to` address. Inbound mail starts when the project's `email/` handlers and recipient rule are ready; run `bwf email alias` to check.
|
|
68
|
+
|
|
69
|
+
## `bwf email domain` {#nosam-email-domain}
|
|
70
|
+
|
|
71
|
+
```
|
|
72
|
+
bwf email domain <add|status|list|sync|rotate-secret|remove> [<domain>] [--project <name>]
|
|
73
|
+
```
|
|
74
|
+
|
|
75
|
+
Send and receive at your own domain on a Cloudflare zone you own, registered to the project. bwf platform only — on your own Cloudflare account the mail domain comes from `email.from` instead (see `bwf email setup`). The walkthrough is [Your own domain on the platform](../../guide/email/domains.md#your-own-domain-on-the-platform).
|
|
76
|
+
|
|
77
|
+
### `bwf email domain add` {#nosam-email-domain-add}
|
|
78
|
+
|
|
79
|
+
```
|
|
80
|
+
bwf email domain add <domain> [--project <name>]
|
|
81
|
+
```
|
|
82
|
+
|
|
83
|
+
Register an exact domain with the project using a scoped Cloudflare API token. The CLI opens a token template, accepts a masked paste or newly copied token, and asks you to confirm account and zone restrictions. Credentials are encrypted for the zone connection. Custom inbound email requires a Cloudflare zone apex because its catch-all does not cover subdomains. Foreign MX records and catch-alls are preserved; use another zone apex or the platform shared mail address when the apex already receives mail. Each custom apex belongs to one project. Setup returns an operation ID so an interrupted request can be checked without restarting the operation.
|
|
84
|
+
|
|
85
|
+
### `bwf email domain status` {#nosam-email-domain-status}
|
|
86
|
+
|
|
87
|
+
```
|
|
88
|
+
bwf email domain status <domain> [--project <name>]
|
|
89
|
+
```
|
|
90
|
+
|
|
91
|
+
Show the recorded inbound, outbound, and management readiness, observation times, and latest operation. Use `sync` to reconcile setup and refresh readiness.
|
|
92
|
+
|
|
93
|
+
### `bwf email domain list` {#nosam-email-domain-list}
|
|
94
|
+
|
|
95
|
+
```
|
|
96
|
+
bwf email domain list [--project <name>]
|
|
97
|
+
```
|
|
98
|
+
|
|
99
|
+
List the project's registered email domains and readiness.
|
|
100
|
+
|
|
101
|
+
### `bwf email domain sync` {#nosam-email-domain-sync}
|
|
102
|
+
|
|
103
|
+
```
|
|
104
|
+
bwf email domain sync <domain> [--project <name>]
|
|
105
|
+
```
|
|
106
|
+
|
|
107
|
+
Reconcile the domain connection and refresh readiness. Sync does not rotate its secret. A blocked or uncertain operation exits unsuccessfully and names the operation to inspect.
|
|
108
|
+
|
|
109
|
+
### `bwf email domain rotate-secret` {#nosam-email-domain-rotate-secret}
|
|
110
|
+
|
|
111
|
+
```sh
|
|
112
|
+
bwf email domain rotate-secret <domain> [--project <name>]
|
|
113
|
+
```
|
|
114
|
+
|
|
115
|
+
Rotate the connection secret shared by this domain and other domains on the same zone. Inbound delivery must be ready; run `bwf email domain sync <domain>` first if setup is incomplete. Inspect an uncertain result before retrying.
|
|
116
|
+
|
|
117
|
+
### `bwf email domain remove` {#nosam-email-domain-remove}
|
|
118
|
+
|
|
119
|
+
```
|
|
120
|
+
bwf email domain remove <domain> [--project <name>]
|
|
121
|
+
```
|
|
122
|
+
|
|
123
|
+
Disable the domain assignment and record cleanup. Zone resources used by another domain remain available. Unfinished or uncertain cleanup remains recorded until it can be reconciled safely.
|
|
124
|
+
|
|
125
|
+
## `bwf email status` {#nosam-email-status}
|
|
126
|
+
|
|
127
|
+
```
|
|
128
|
+
bwf email status --platform cloudflare
|
|
129
|
+
```
|
|
130
|
+
|
|
131
|
+
Check the domain configured in `email.from`: permissions, DNS, routing, sending, handler addresses, and the email binding. Exits unsuccessfully when setup is incomplete. Workers Free setup can be ready with sending limited to verified destinations; run `bwf email setup --platform cloudflare` after upgrading to Workers Paid.
|
|
132
|
+
|
|
133
|
+
`bwf email status` reads only your own Cloudflare account, so `--platform cloudflare` is required. On the bwf platform, use `bwf email usage` and `bwf email destinations`.
|
|
134
|
+
|
|
135
|
+
## `bwf email setup` {#nosam-email-setup}
|
|
136
|
+
|
|
137
|
+
```
|
|
138
|
+
bwf email setup --platform cloudflare
|
|
139
|
+
```
|
|
140
|
+
|
|
141
|
+
Set up email before deploying from CI. Requires `email.from` in `bwf.config.ts`, an interactive terminal, and Cloudflare email permissions.
|
|
142
|
+
|
|
143
|
+
bwf shows the planned DNS, routing, plus-addressing, and sending changes and asks before applying them. Commit `bwf.lock.json`, then run `bwf deploy --platform cloudflare --require-email` in CI.
|
|
144
|
+
|
|
145
|
+
On Workers Free, inbound mail and sends to verified recipients remain available. Run this command again after upgrading to Workers Paid to enable arbitrary recipients. See [Email setup](../../guide/email/domains.md#your-own-cloudflare-account).
|
|
@@ -0,0 +1,113 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: 'Scaffold a Drizzle table and the routes that list, create, and fetch a row.'
|
|
3
|
+
outline: deep
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# Code Generation {#code-generation}
|
|
7
|
+
|
|
8
|
+
## `bwf gen model` {#nosam-gen-model}
|
|
9
|
+
|
|
10
|
+
```
|
|
11
|
+
bwf gen model <name> [columns...]
|
|
12
|
+
```
|
|
13
|
+
|
|
14
|
+
Scaffold a Drizzle table, list and create routes, and a route to fetch one row by ID.
|
|
15
|
+
|
|
16
|
+
```sh
|
|
17
|
+
bwf gen model posts title:string body:text published:boolean
|
|
18
|
+
```
|
|
19
|
+
|
|
20
|
+
Creates:
|
|
21
|
+
|
|
22
|
+
- `db/schema/posts.ts`: a table with `id`, `createdAt`, `updatedAt`, and your columns
|
|
23
|
+
- An export from `db/schema.ts`
|
|
24
|
+
- `routes/api/posts/index.ts`: `GET` for list and `POST` for insert with validation
|
|
25
|
+
- `routes/api/posts/[id].ts`: `GET` by id with `404` handling
|
|
26
|
+
- Regenerated types and TypeScript configuration in `.bwf/`
|
|
27
|
+
|
|
28
|
+
The generated routes automatically detect your validation library from `package.json` (`valibot`, `zod`, or `arktype`). If none is found, you will be prompted to choose one or skip validation. Run `bwf db push` to apply the schema locally, or `bwf db generate` to create migrations before deploying.
|
|
29
|
+
|
|
30
|
+
Column format: `name:type` or `name:type?` (nullable). Types: `string`, `text`, `datetime`, `integer`, `boolean`, `real`, `blob`.
|
|
31
|
+
|
|
32
|
+
Model names must be lowercase alphanumeric with underscores (e.g. `posts`, `user_roles`). Existing files are never overwritten.
|
|
33
|
+
|
|
34
|
+
## `bwf gen migration` {#nosam-gen-migration}
|
|
35
|
+
|
|
36
|
+
```
|
|
37
|
+
bwf gen migration <name>
|
|
38
|
+
```
|
|
39
|
+
|
|
40
|
+
Create an empty migration file with a timestamp prefix (`YYYYMMDDHHMMSS`).
|
|
41
|
+
|
|
42
|
+
```sh
|
|
43
|
+
bwf gen migration add_avatar_to_users
|
|
44
|
+
# → db/migrations/20260410161500_add_avatar_to_users.sql
|
|
45
|
+
```
|
|
46
|
+
|
|
47
|
+
Existing projects using the old numeric prefix (`0001_`, `0002_`, ...) can rename with `bwf db rename-migrations`.
|
|
48
|
+
|
|
49
|
+
## `bwf gen route` {#nosam-gen-route}
|
|
50
|
+
|
|
51
|
+
```
|
|
52
|
+
bwf gen route <path> [--methods get,post,...]
|
|
53
|
+
```
|
|
54
|
+
|
|
55
|
+
Create a route file with `defineHandler` exports. Defaults to GET.
|
|
56
|
+
|
|
57
|
+
```sh
|
|
58
|
+
bwf gen route api/health
|
|
59
|
+
bwf gen route api/users --methods get,post,delete
|
|
60
|
+
```
|
|
61
|
+
|
|
62
|
+
Creates `routes/<path>.ts` with an exported handler for each method. Supported methods: `get`, `post`, `put`, `patch`, `delete`.
|
|
63
|
+
|
|
64
|
+
## `bwf gen middleware` {#nosam-gen-middleware}
|
|
65
|
+
|
|
66
|
+
```
|
|
67
|
+
bwf gen middleware <name>
|
|
68
|
+
```
|
|
69
|
+
|
|
70
|
+
Create a numbered middleware file with `defineMiddleware` default export.
|
|
71
|
+
|
|
72
|
+
```sh
|
|
73
|
+
bwf gen middleware auth
|
|
74
|
+
# → middleware/01.auth.ts (or 02, 03, etc.)
|
|
75
|
+
```
|
|
76
|
+
|
|
77
|
+
The prefix is auto-detected from existing middleware files.
|
|
78
|
+
|
|
79
|
+
## `bwf gen cron` {#nosam-gen-cron}
|
|
80
|
+
|
|
81
|
+
```
|
|
82
|
+
bwf gen cron <name>
|
|
83
|
+
```
|
|
84
|
+
|
|
85
|
+
Create a cron job file in `crons/` with `defineScheduled` and a placeholder cron expression.
|
|
86
|
+
|
|
87
|
+
```sh
|
|
88
|
+
bwf gen cron hourly-sync
|
|
89
|
+
```
|
|
90
|
+
|
|
91
|
+
## `bwf gen queue` {#nosam-gen-queue}
|
|
92
|
+
|
|
93
|
+
```
|
|
94
|
+
bwf gen queue <name>
|
|
95
|
+
```
|
|
96
|
+
|
|
97
|
+
Create a queue consumer file in `queues/` with `defineQueue`, a `Message` type, and commented-out batch options.
|
|
98
|
+
|
|
99
|
+
```sh
|
|
100
|
+
bwf gen queue emails
|
|
101
|
+
```
|
|
102
|
+
|
|
103
|
+
## `bwf gen procedure` {#nosam-gen-procedure}
|
|
104
|
+
|
|
105
|
+
```
|
|
106
|
+
bwf gen procedure <file.name>
|
|
107
|
+
```
|
|
108
|
+
|
|
109
|
+
Create a procedure in `procedures/`. The last word is the export and the rest is the file, so `contacts.get` adds a `get` export to `procedures/contacts.ts`, and `billing.invoices.list` adds `list` to `procedures/billing/invoices.ts`. The file lists the decisions each procedure must make before it can deploy.
|
|
110
|
+
|
|
111
|
+
```sh
|
|
112
|
+
bwf gen procedure contacts.get
|
|
113
|
+
```
|
|
@@ -0,0 +1,181 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: 'Connect GitHub so pushes build and deploy, whichever way you signed in to bwf.'
|
|
3
|
+
outline: deep
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# GitHub and Builds {#github}
|
|
7
|
+
|
|
8
|
+
Deploy-on-GitHub works from **any** bwf login — Google, GitHub, or other SSO. The first time you connect GitHub, bwf links your GitHub identity to your current account (a one-time step, independent of how you logged in); it never creates a second account.
|
|
9
|
+
|
|
10
|
+
Project-scoped `github` and `build` commands resolve the project in the same order as deploy: the `[project]` argument or `--project`, then `BWF_PROJECT`, then the linked project (`.bwf/project.json`).
|
|
11
|
+
|
|
12
|
+
## `bwf github link` {#nosam-github-link}
|
|
13
|
+
|
|
14
|
+
```
|
|
15
|
+
bwf github link
|
|
16
|
+
```
|
|
17
|
+
|
|
18
|
+
Link your signed-in bwf account to GitHub through your browser. `bwf github install` does this automatically when needed.
|
|
19
|
+
|
|
20
|
+
::: warning Existing GitHub sign-in
|
|
21
|
+
A GitHub identity can belong to only one bwf account. If it is already linked elsewhere, sign in to that bwf account or authorize a different GitHub identity.
|
|
22
|
+
:::
|
|
23
|
+
|
|
24
|
+
## `bwf github install` {#nosam-github-install}
|
|
25
|
+
|
|
26
|
+
```
|
|
27
|
+
bwf github install
|
|
28
|
+
```
|
|
29
|
+
|
|
30
|
+
Open the GitHub App install page in your browser. If your account has no linked GitHub identity yet, `bwf github install` first runs the GitHub link automatically (browser authorize), then continues. After installing, run `bwf github connect` to link a repository to your project.
|
|
31
|
+
|
|
32
|
+
## `bwf github installations` {#nosam-github-installations}
|
|
33
|
+
|
|
34
|
+
```
|
|
35
|
+
bwf github installations
|
|
36
|
+
```
|
|
37
|
+
|
|
38
|
+
List all GitHub App installations linked to your account. Each entry includes the `[id: <installation_id>]` needed for `--installation` in non-interactive use.
|
|
39
|
+
|
|
40
|
+
## `bwf github join` {#nosam-github-join}
|
|
41
|
+
|
|
42
|
+
```
|
|
43
|
+
bwf github join
|
|
44
|
+
```
|
|
45
|
+
|
|
46
|
+
Join an existing organization installation through your browser. `bwf github connect` can do this automatically in an interactive terminal. Run `join` locally before non-interactive setup when needed.
|
|
47
|
+
|
|
48
|
+
Requires a signed-in bwf account and organization-installation sharing enabled by your platform. Use `bwf github installations` to find the installation ID.
|
|
49
|
+
|
|
50
|
+
## `bwf github connect` {#nosam-github-connect}
|
|
51
|
+
|
|
52
|
+
```
|
|
53
|
+
bwf github connect [project] [options]
|
|
54
|
+
```
|
|
55
|
+
|
|
56
|
+
Connect a GitHub repository to a bwf project for automatic deploys. On every push to the configured branch, bwf builds and deploys your project automatically.
|
|
57
|
+
|
|
58
|
+
The CLI opens your browser when it needs GitHub authorization. If no installation is available, run `bwf github install`.
|
|
59
|
+
|
|
60
|
+
**Options**
|
|
61
|
+
|
|
62
|
+
| Flag | Description |
|
|
63
|
+
| --------------------- | -------------------------------------------------------------------------------- |
|
|
64
|
+
| `--project <name>` | Project name (alias for the positional argument) |
|
|
65
|
+
| `--installation <id>` | GitHub App installation ID (required when you have multiple installations) |
|
|
66
|
+
| `--repo <owner/repo>` | Repository full name — required unless the installation grants exactly one repo |
|
|
67
|
+
| `--branch <name>` | Branch to deploy from — **required in non-interactive mode** |
|
|
68
|
+
| `--executor <type>` | Build executor: `container` (default) or `github_actions` |
|
|
69
|
+
| `--workflow <path>` | Authorized deploy workflow file — defaults to `.github/workflows/bwf-deploy.yml` |
|
|
70
|
+
|
|
71
|
+
Choose `container` for platform builds or `github_actions` for a deployment workflow. The CLI prompts for the executor and, for GitHub Actions, the workflow file. Pass the corresponding flags to skip those prompts.
|
|
72
|
+
|
|
73
|
+
The workflow must be a `.yml` or `.yaml` file under `.github/workflows/`. Only that workflow can obtain the project's OIDC deployment token. Prefer a dedicated deployment workflow.
|
|
74
|
+
|
|
75
|
+
For CI, supply the project and branch, plus the installation and repository when they cannot be selected automatically. Organization connections require repository authorization in a local browser first.
|
|
76
|
+
|
|
77
|
+
```
|
|
78
|
+
bwf github connect my-app \
|
|
79
|
+
--installation 42 \
|
|
80
|
+
--repo owner/my-app \
|
|
81
|
+
--branch main
|
|
82
|
+
```
|
|
83
|
+
|
|
84
|
+
You can connect only repositories your GitHub account can access.
|
|
85
|
+
|
|
86
|
+
A project has one GitHub connection. Running `bwf github connect` on a project that is already connected fails. To connect a different repository, run `bwf github disconnect` first.
|
|
87
|
+
|
|
88
|
+
## `bwf github update` {#nosam-github-update}
|
|
89
|
+
|
|
90
|
+
```
|
|
91
|
+
bwf github update [project] [options]
|
|
92
|
+
```
|
|
93
|
+
|
|
94
|
+
Change the branch, executor, or workflow for an existing connection. To change the repository, disconnect and reconnect.
|
|
95
|
+
|
|
96
|
+
**Options**
|
|
97
|
+
|
|
98
|
+
| Flag | Description |
|
|
99
|
+
| ------------------- | ---------------------------------------------------------------- |
|
|
100
|
+
| `--project <name>` | Project name (alias for the positional argument) |
|
|
101
|
+
| `--branch <name>` | New branch to deploy from |
|
|
102
|
+
| `--executor <type>` | New build executor: `container` or `github_actions` |
|
|
103
|
+
| `--workflow <path>` | New authorized deploy workflow file (under `.github/workflows/`) |
|
|
104
|
+
|
|
105
|
+
The CLI prompts for new settings using the current values as defaults. In CI, pass at least one of `--branch`, `--executor`, or `--workflow`.
|
|
106
|
+
|
|
107
|
+
```
|
|
108
|
+
bwf github update my-app --executor github_actions
|
|
109
|
+
```
|
|
110
|
+
|
|
111
|
+
## `bwf github status` {#nosam-github-status}
|
|
112
|
+
|
|
113
|
+
```
|
|
114
|
+
bwf github status [project]
|
|
115
|
+
```
|
|
116
|
+
|
|
117
|
+
Show the connected repository, branch, executor, and workflow. Container builds do not use the workflow file.
|
|
118
|
+
|
|
119
|
+
**Options**
|
|
120
|
+
|
|
121
|
+
| Flag | Description |
|
|
122
|
+
| ------------------ | ------------------------------------------------ |
|
|
123
|
+
| `--project <name>` | Project name (alias for the positional argument) |
|
|
124
|
+
|
|
125
|
+
```
|
|
126
|
+
bwf github status my-app
|
|
127
|
+
```
|
|
128
|
+
|
|
129
|
+
## `bwf github disconnect` {#nosam-github-disconnect}
|
|
130
|
+
|
|
131
|
+
```
|
|
132
|
+
bwf github disconnect [project]
|
|
133
|
+
```
|
|
134
|
+
|
|
135
|
+
Disconnect a project from its GitHub repository, stopping automatic deploys. Any in-flight builds for the project are cancelled before the connection is removed. If the project has no connection, it reports that and exits successfully. To point a project at a different repository, disconnect first, then run `bwf github connect`.
|
|
136
|
+
|
|
137
|
+
You are asked to confirm before anything is removed. Pass `--yes` to skip the prompt; `--yes` is **required** in a non-interactive shell (CI), where there is no prompt to answer.
|
|
138
|
+
|
|
139
|
+
**Options**
|
|
140
|
+
|
|
141
|
+
| Flag | Description |
|
|
142
|
+
| ------------------ | ----------------------------------------------------------------- |
|
|
143
|
+
| `--project <name>` | Project name (alias for the positional argument) |
|
|
144
|
+
| `--yes` | Skip the confirmation prompt (required in non-interactive shells) |
|
|
145
|
+
|
|
146
|
+
```
|
|
147
|
+
bwf github disconnect my-app --yes
|
|
148
|
+
```
|
|
149
|
+
|
|
150
|
+
## Build {#build}
|
|
151
|
+
|
|
152
|
+
Inspect Deploy-on-GitHub builds.
|
|
153
|
+
|
|
154
|
+
### `bwf build logs` {#nosam-build-logs}
|
|
155
|
+
|
|
156
|
+
```
|
|
157
|
+
bwf build logs [build] [--follow] [--output <file>] [--project <slug>]
|
|
158
|
+
```
|
|
159
|
+
|
|
160
|
+
Stream, tail, or download the build logs for a **container** build. With no
|
|
161
|
+
`[build]` argument, targets the project's most recent build.
|
|
162
|
+
|
|
163
|
+
| Flag | Purpose | Default |
|
|
164
|
+
| ------------------------ | ------------------------------------------------------------------------- | ------- |
|
|
165
|
+
| `--follow`, `-f` | Live-tail: poll until the build finishes and its final logs are captured. | off |
|
|
166
|
+
| `--output <file>`, `-o` | Write logs to a file instead of stdout (appends while following). | stdout |
|
|
167
|
+
| `--project <slug>`, `-p` | Target project. | linked |
|
|
168
|
+
|
|
169
|
+
Builds run on **GitHub Actions** keep their logs on GitHub — the command prints
|
|
170
|
+
the Actions run URL instead of streaming. Only the last 10,000 log lines of a
|
|
171
|
+
container build are retained.
|
|
172
|
+
|
|
173
|
+
Following waits for the platform to confirm the final log tail. If the platform cannot confirm it, upgrade the platform runtime or read the retained logs without `--follow`. An unfinished final tail reports an error after two minutes; retry to recover it.
|
|
174
|
+
|
|
175
|
+
Examples:
|
|
176
|
+
|
|
177
|
+
```
|
|
178
|
+
bwf build logs # print the latest build's logs
|
|
179
|
+
bwf build logs -f # follow the latest build until it finishes
|
|
180
|
+
bwf build logs bld_123 -o build.log # download a specific build's logs
|
|
181
|
+
```
|
|
@@ -0,0 +1,93 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: 'Create and edit platform plans and their limits from an administrator session.'
|
|
3
|
+
outline: deep
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# Platform Configuration {#plan-configuration}
|
|
7
|
+
|
|
8
|
+
Use your administrator session for these commands. See [Platform Management](./platform.md#operator-commands) for platform selection, previews, and confirmation.
|
|
9
|
+
|
|
10
|
+
`bwf platform config plans` opens an interactive plan menu using your administrator session. Plans have stable IDs and editable display names. Copy an existing plan to add one, edit limits without redeploying, archive it to stop new assignments, or remove it with an explicit replacement for its accounts.
|
|
11
|
+
|
|
12
|
+
```sh
|
|
13
|
+
bwf platform config plans show [plan-id]
|
|
14
|
+
bwf platform config plans add <plan-id> --copy <existing-id> --name "Team"
|
|
15
|
+
bwf platform config plans set <plan-id> [--name "Team"] [--file plan.json]
|
|
16
|
+
bwf platform config plans reset <builtin-plan-id>
|
|
17
|
+
bwf platform config plans archive <plan-id>
|
|
18
|
+
bwf platform config plans restore <plan-id>
|
|
19
|
+
bwf platform config plans remove <plan-id> [--replacement <plan-id>]
|
|
20
|
+
bwf platform config plans default <plan-id>
|
|
21
|
+
bwf platform config plans sync
|
|
22
|
+
```
|
|
23
|
+
|
|
24
|
+
Use `--plan` to preview changes and affected accounts; scripted mutations require `--yes`. Every command supports `--connection <slug-or-url>` and `--json`. `show` reports the effective limits, default, assignments, and pending account and AI logging updates. `show <plan-id>` also reports the plan's AI Gateway logging default. `reset` restores a built-in plan's original limits and build instance size. Archived plans keep their existing accounts but cannot receive new assignments; change the default before archiving it. `remove` requires a replacement for a plan that has accounts or is the default. Changing the default affects new accounts, plus the AI Gateway logging of accounts whose plan is not in the catalog.
|
|
25
|
+
|
|
26
|
+
For `add` and `set`, `--file` reads a JSON object with optional `name`, `limits`, `buildInstanceType`, and boolean `allowShortSlugs`. `limits` is a partial object of nonnegative whole numbers; `0` means unlimited by the plan. Build timeouts remain capped at the platform maximum of 60 minutes; `0` uses that maximum. Omitted settings keep their current values or the copied plan's values. `buildInstanceType` is `standard-3` or `standard-4`. `allowShortSlugs` permits future assignments of project slugs of five characters or fewer; existing URLs remain available. `aiLogging` sets the plan's [AI Gateway logging](./platform-users.md#ai-gateway-logging) default: `off`, `metadata`, or `full`. `"inherit"` clears it; leaving it out keeps the current value. Storage quotas are not editable. See [Plans and Limits](../../guide/platform/administration/plans.md) for supported limits and examples.
|
|
27
|
+
|
|
28
|
+
An apply checks the preview's revision and rejects concurrent changes. Lower quotas can restrict accounts already above them; usage history and billing periods are preserved. The CLI continues account updates and AI logging publishing until complete, then prints how many projects received the AI logging default and when new requests are expected to follow it. If an update fails or stops making progress, the configuration remains saved and the command exits unsuccessfully. Run `sync --yes` to continue before editing plans again. Inspect `show` and operator events after an uncertain request outcome.
|
|
29
|
+
|
|
30
|
+
## Authentication configuration {#authentication-configuration}
|
|
31
|
+
|
|
32
|
+
`bwf platform config auth` opens interactive configuration. These commands use
|
|
33
|
+
your administrator session from `bwf platform auth login`:
|
|
34
|
+
|
|
35
|
+
```sh
|
|
36
|
+
bwf platform config auth list
|
|
37
|
+
bwf platform config auth show company
|
|
38
|
+
bwf platform config auth add google
|
|
39
|
+
bwf platform config auth add oidc --id company
|
|
40
|
+
bwf platform config auth add cloudflare-access --id access
|
|
41
|
+
bwf platform config auth configure company
|
|
42
|
+
bwf platform config auth test company
|
|
43
|
+
bwf platform config auth link company
|
|
44
|
+
bwf platform config auth enable company
|
|
45
|
+
bwf platform config auth disable github
|
|
46
|
+
bwf platform config auth admission
|
|
47
|
+
bwf platform config auth protection show
|
|
48
|
+
bwf platform config auth protection enable --installation <id>
|
|
49
|
+
bwf platform config auth protection disable --installation <id>
|
|
50
|
+
bwf platform config auth recover company --installation <id> --file recovery.json
|
|
51
|
+
```
|
|
52
|
+
|
|
53
|
+
When configuring an existing installation for the first time, run
|
|
54
|
+
`bwf platform config auth initialize`, then sign in again. Its current login
|
|
55
|
+
methods and signup policy are preserved.
|
|
56
|
+
|
|
57
|
+
Adding or editing a method saves a pending configuration. Enabling it verifies the
|
|
58
|
+
login in your browser before applying it. Linking the verified identity to your
|
|
59
|
+
account is a separate, explicit action. Before disabling a method, verify a linked
|
|
60
|
+
alternative; the last method cannot be disabled. Disabling revokes human sessions
|
|
61
|
+
created through that method, including operator sessions. Scoped deployment tokens
|
|
62
|
+
remain valid; a human login token used as `BWF_TOKEN` is still revoked.
|
|
63
|
+
|
|
64
|
+
Commands accept `--connection <slug-or-url>` and `--json`. Changes accept
|
|
65
|
+
`--plan` or `--yes`. For scripted configuration, use `--file <path>` for the
|
|
66
|
+
nonsecret fields and `--client-secret-env <name>` for the environment variable
|
|
67
|
+
containing the secret. Omit the secret when editing to retain its saved value.
|
|
68
|
+
For `enable` or `link` in scripts, supply `--test-id <id>` from a completed test.
|
|
69
|
+
`test --json` returns a browser URL, test ID, and expiry without waiting for completion.
|
|
70
|
+
|
|
71
|
+
`admission` chooses invited/allowlisted, company-approved, or public signup.
|
|
72
|
+
Company-approved signup creates ordinary accounts automatically when a user
|
|
73
|
+
passes a configured company rule. Select an enabled, company-restricted OIDC or
|
|
74
|
+
Google Workspace method, or an enabled Cloudflare Access gate. In scripts,
|
|
75
|
+
`admission --file <path> --yes` reads a policy such as
|
|
76
|
+
`{"mode":"company","connections":["company"],"access":false}`.
|
|
77
|
+
|
|
78
|
+
`protection enable` creates or connects Cloudflare Access applications independently
|
|
79
|
+
of login methods. Its `--file` accepts the `cloudflareAccess` object described in
|
|
80
|
+
[installation setup](../../guide/platform/installation/setup.md#choose-login-methods).
|
|
81
|
+
Protection changes require installation ownership, the saved recovery credentials,
|
|
82
|
+
and a human administrator session. They revoke current human sessions. Before
|
|
83
|
+
removing protection, change any signup rule that depends on that gate. Cloudflare
|
|
84
|
+
applications are retained for deliberate cleanup.
|
|
85
|
+
|
|
86
|
+
`recover <connection-id>` restores an existing administrator when normal login is
|
|
87
|
+
unavailable. Its file contains `administratorUserId`, optional nonsecret provider
|
|
88
|
+
`configuration`, and an `expectedIdentity` object with exact `issuer` and `subject`
|
|
89
|
+
when using `--yes`. Recovery requires Cloudflare management/database authority,
|
|
90
|
+
original recovery keys, and a successful browser provider test. Use
|
|
91
|
+
`--client-secret-env <name>` for new or rotated credentials.
|
|
92
|
+
|
|
93
|
+
For automation, see [operator authentication](./platform.md#operator-authentication).
|
|
@@ -0,0 +1,81 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: 'Administer platform email, including the shared sender and project recipient rules.'
|
|
3
|
+
outline: deep
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# Platform Email {#operator-email}
|
|
7
|
+
|
|
8
|
+
Use your administrator session for these commands. See [Platform Management](./platform.md#operator-commands) for platform selection, previews, and confirmation.
|
|
9
|
+
|
|
10
|
+
Decide who mail from the shared sender may reach, who registers email domains, and a project's outbound caps:
|
|
11
|
+
|
|
12
|
+
```sh
|
|
13
|
+
bwf platform email policy
|
|
14
|
+
bwf platform email policy-set <verified|domains|any> [--domains <domain[,domain...]>]
|
|
15
|
+
bwf platform email settings
|
|
16
|
+
bwf platform email settings-set --domains <self-serve|admin>
|
|
17
|
+
bwf platform email limit <project-id|slug> [--monthly <n>] [--burst <n>]
|
|
18
|
+
bwf platform email logs <project-id|slug> [--page <n>] [--limit <n>] [--json]
|
|
19
|
+
bwf platform email attempts [--project <id|slug>] [--page <n>] [--limit <n>]
|
|
20
|
+
bwf platform email attempt-resolve <attempt-id> --ended --reason <text>
|
|
21
|
+
bwf platform email operation-resolve <operation-id> --ended --outcome <applied|not-applied> --reason <text>
|
|
22
|
+
bwf platform email shared-recipients [--project <id|slug>] [--page <n>] [--limit <n>]
|
|
23
|
+
bwf platform email shared-recipient-resolve <recipient-id> --ended --outcome <applied|not-applied> --reason <text>
|
|
24
|
+
```
|
|
25
|
+
|
|
26
|
+
`policy` decides which recipients a project's `<slug>+tag@<mail domain>` sender reaches: `verified` (the default) means only that project's verified destinations; `domains` adds every address on the listed domains; `any` lifts the check. Neither widens delivery to addresses on the platform's own mail domain: those stay verified-destination-only, so no project reaches another project's inbox without its consent. Cloudflare still refuses a destination it has not verified until the platform mail domain is onboarded for Email Sending, so under `domains` or `any` such refusals arrive as per-recipient `UNVERIFIED_DESTINATION` results. Custom-domain sends are not affected.
|
|
27
|
+
|
|
28
|
+
`settings-set --domains admin` tells `bwf email domain add` to print the administrator's command instead of starting token setup. `limit` overrides the project's monthly and rolling 60-second caps (defaults 200 and 10); a project page in the admin UI shows and clears them.
|
|
29
|
+
|
|
30
|
+
`logs` inspects retained receipt and recipient outcomes, including operation IDs, provider references, error codes, and policy versions. Pages contain at most 100 records, newest first; use `--json` for all fields. After project deletion, use its project ID to inspect metadata until the 30-day retention period expires. Message content and credentials are never included.
|
|
31
|
+
|
|
32
|
+
`attempts` lists interrupted provider calls and their earliest resolution time. Once
|
|
33
|
+
the original Worker execution has ended and the attempt is at least 24 hours old,
|
|
34
|
+
`attempt-resolve` records `outcome_unknown`, retains its quota charge, and releases
|
|
35
|
+
the project/domain cleanup fence. `--ended` is your attestation that the call is no
|
|
36
|
+
longer active; `--reason` is stored in the operator audit log. Keep recipient
|
|
37
|
+
addresses and message content out of the reason. The send is never retried. Use
|
|
38
|
+
`--plan` to preview and `--yes` to apply without a prompt.
|
|
39
|
+
|
|
40
|
+
`operation-resolve` recovers a Cloudflare routing, Worker, secret, catch-all, or
|
|
41
|
+
Sending mutation whose outcome remains unknown. After the original execution
|
|
42
|
+
has ended and the operation is at least 24 hours old, inspect the exact resource
|
|
43
|
+
named by the preview and attest whether its write was `applied` or `not-applied`.
|
|
44
|
+
Applied writes continue at the next step; not-applied writes retry the same
|
|
45
|
+
persisted intent. The running platform version must match that intent, so restore
|
|
46
|
+
the matching version before recovering an operation created by older code. Time
|
|
47
|
+
alone never retries a write.
|
|
48
|
+
|
|
49
|
+
`shared-recipients` discovers shared inbound addresses, provider rule names and
|
|
50
|
+
IDs, and interrupted creation intents, including projects awaiting deletion.
|
|
51
|
+
If creation has an unknown outcome, use `shared-recipient-resolve` after the
|
|
52
|
+
original execution has ended and its creation intent is at least 24 hours old.
|
|
53
|
+
Inspect the exact account, zone, recipient and rule named by `--plan`, and use
|
|
54
|
+
Cloudflare's provider audit to establish whether creation was `applied` or
|
|
55
|
+
`not-applied`. A missing rule alone is insufficient evidence for `not-applied`.
|
|
56
|
+
Supply that finding in `--reason`; it is recorded in platform events.
|
|
57
|
+
|
|
58
|
+
Applied recovery requires the exact owned rule to be present and records its
|
|
59
|
+
ID. Not-applied recovery releases the creation intent only after repeated
|
|
60
|
+
provider inspection and your attestation. Both outcomes leave delivery unready
|
|
61
|
+
until normal reconciliation verifies it. Recovery itself creates or deletes no
|
|
62
|
+
provider rule and never reopens a deleting project; retry deletion afterward
|
|
63
|
+
when recovering cleanup. Use `--yes` to apply the preview without a prompt.
|
|
64
|
+
If the intent or provider ownership changes, inspect a new plan.
|
|
65
|
+
|
|
66
|
+
Register and maintain email domains for projects whose owners hold no Cloudflare credential:
|
|
67
|
+
|
|
68
|
+
```sh
|
|
69
|
+
bwf platform email domains [--project <id|slug>]
|
|
70
|
+
bwf platform email domain-add <domain> --project <id|slug> [--token-stdin] [--outbound-only]
|
|
71
|
+
bwf platform email domain-status <domain>
|
|
72
|
+
bwf platform email domain-sync <domain>
|
|
73
|
+
bwf platform email domain-rotate-secret <domain>
|
|
74
|
+
bwf platform email domain-remove <domain> [--token-stdin]
|
|
75
|
+
```
|
|
76
|
+
|
|
77
|
+
`domain-add` uses the platform's Cloudflare credential for zones in its account. For another account, pipe a scoped Cloudflare API token on standard input with `--token-stdin --yes`. Managed custom inbound email requires the Cloudflare zone apex (`example.com`). If its MX records already belong to another mail provider, such as Microsoft 365 or Google Workspace, add `--outbound-only` to send from the apex while that provider keeps receiving its mail; see [Sending from a domain that already receives mail](../../guide/platform/administration/email.md#sending-from-a-domain-that-already-receives-mail). Otherwise use the project's shared email address or choose another unused zone. Native Cloudflare deployments also support literal recipient addresses on subdomains; see [Your own Cloudflare account](../../guide/email/domains.md#your-own-cloudflare-account).
|
|
78
|
+
|
|
79
|
+
`domain-status` shows inbound, outbound, and credential-management readiness with the latest operation. A blocked operation resumes through `domain-sync`; a blocked rotation resumes through `domain-rotate-secret`, preserving already confirmed steps and its staged credential. An uncertain operation remains stopped until read-back proves the result or an administrator uses `operation-resolve`. Domains an administrator adds show `managed_by: admin`; their owners can list and inspect them but use these commands for `sync`, `domain-rotate-secret`, and `remove`.
|
|
80
|
+
|
|
81
|
+
If project deletion leaves cleanup blocked by an expired or revoked Cloudflare token, use `domain-remove <domain> --token-stdin --yes` with a replacement scoped to the same account and zone. This resumes the retained cleanup only when no other project uses the connection. For a live project, renew its token through `domain-add` instead.
|