Production and deployment
Complete the production review
Review compatibility dates, runtime limits, costs, permissions, storage semantics, recovery, and ownership before calling Link Vault production-ready.
8 minute lesson
Platform capabilities and plan limits evolve. The production review must consult current official documentation rather than trust numbers copied into an old checklist.
Confirm the compatibility date, binding targets, environment separation, secret access, resource limits, current pricing, cache consistency, D1 recovery, queue retries, R2 lifecycle, logs, alerts, and a tested rollback. Remove unused products and permissions.
Turn the checklist into evidence: the deployed version ID, binding names and resource owners, latest restore test, smoke-test output, alert destination, and the person who can execute recovery. A checkbox without a command, link, or observation quickly becomes ceremonial.
Review failure boundaries as a whole. Code rollback does not restore data, cache invalidation is not immediate, background work can be delivered more than once, and an expired credential can break an older version. Set budgets and alerts from current plan documentation, then remove resources, routes, secrets, and permissions the application no longer needs. Finish by having someone other than the author follow the runbook.
Run the checklist against staging, deploy a version, create and export one link, inspect logs, then exercise the rollback plan.
Lesson completed