Expand description
bynk deploy — provision persistent Cloudflare identity, then publish.
The generated wrangler.toml is deliberately disposable. This module owns
the small, committed bynk.deploy.lock ledger and materialises its KV id
into a freshly compiled worker immediately before Wrangler sees it.
The command mints real Cloudflare resources and writes secrets, so it is
split by concern rather than kept as one file — following the layout
bynk-emit/src/project.rs established: this parent carries the shared
imports, the mod declarations, and the re-exports external callers see,
while each child opens with use super::*; and documents its own items.
config.rs— the generatedwrangler.toml/ build-output model, and the[env.<name>]synthesis a non-default--envneeds.graph.rs— the binding graph, the upload order it forces, and the deploy-time contract-skew check.ledger.rs— the committedbynk.deploy.lock: what this project has provisioned, the orphan diff against it, and--prune.provisioning.rs— every call out to thewranglerCLI.secrets.rs— which secrets a run sets, and where each value comes from.plan.rs— the plan/apply flow that drives all of the above.
Structs§
Enums§
Functions§
- materialise_
deploy_ state - Fill a generated worker configuration from the committed deploy ledger.
This is shared with
bynk dev -- --remote; local dev leaves placeholders alone because Miniflare does not read the Cloudflare namespace id. - run
- Run the slice-0 single-context deployment pipeline.