Scan one full example with the main current config lanes in one place
See one canonical that touches the main current config lanes in a single file, with hover coverage on every property shown in the example.
This page is the quick “show me the whole shape” version of Devflare config. It is intentionally full enough to scan the current top-level lanes in one file without turning into a maximal dump of every possible nested variant.
- Best for
- Seeing the whole current config shape before you zoom into one subsection
- Reading pattern
- Scan the example first, then hover properties, then open the specialist page you actually need
- Important boundary
- This example is canonical, but not every binding family variant is shown inline
Use one canonical example when you want the whole shape in view
When you already know Devflare is split into config, runtime, testing, and framework lanes, the next practical question is often just: what does a full current config actually look like?
That is what this page is for. The example below touches the major current top-level config lanes in one place, while still staying readable enough for code review and copy-with-intent adaptation.
Full does not mean maximal
Every property shown above is real and current, but some binding families accept richer object variants than this page needs to show. Use this page as the canonical shape, then open the dedicated binding or configuration page when you need a deeper variant.
One full config example you can scan top to bottom
Hover any property in the config to see what that lane means. The example is intentionally broad, but the dedicated pages still own the deeper caveats and richer nested variants.
Know what each top-level lane is doing
| Lane | What it owns | Open next when you need more |
|---|---|---|
| , , | Worker identity and runtime posture. | and |
| , , , | The authored Worker shape: surfaces, bindings, and scheduled intent. | , , and |
| , , | Runtime strings, secret declarations, and environment overlays. | |
| , , | Deployment routing, dev WebSocket proxy rules, and static asset delivery. | |
| , , | Operational posture and release-time controls. | |
| , , | Bundler coordination, host integration, and unsupported Wrangler passthrough. | , , and |
Open the specialist page once the full picture is clear
Configuration
Need the authoring rules?
Open config basics when the question is what should live in authored config versus generated output or deploy-time resolution.
Configuration
Need the project shape story?
Open project shape when the main question is how many Worker surfaces or discovery lanes the package should actually own.
Configuration
Need preview or environment overlays?
Use the environments and previews pages when the full config turns into a question about per-lane overrides or preview-scoped resources.
Configuration
Need runtime and deploy posture?
Open runtime and deploy settings when the question is routes, assets, WebSocket proxy rules, observability, limits, or migrations.
Previous
Config basics
Write for humans first, let Devflare merge environments and resolve names later, and treat generated Wrangler-facing files as outputs rather than authoring surfaces.
Next
Project shape
Start with one fetch file, then add routes, background handlers, Durable Objects, assets, and transport rules only when the project genuinely needs them.