references/bindings/configuration.md
Binding Configuration
Confirm the target account, environment, and resource before adding or changing a binding. Keep staging and production resources separate where their data or permissions must be isolated.
| Task | Current documentation | | --- | --- | | Configure storage, compute, platform, and service bindings | Wrangler binding configuration | | Create or inspect resources and manage deployments | Wrangler commands (select the product's commands) | | Configure named environments and non-inheritable bindings | Wrangler environments | | Set non-sensitive configuration | Environment variables | | Set or rotate credentials in a chosen environment | Secrets | | Configure text, data, and Wasm modules in existing projects | Wrangler bundling and configuration | | Choose locally simulated resources or remote bindings | Local development and supported bindings per development mode | | Supply local variables and secrets | Local environment variables and secrets | | Seed or persist local resource data | Adding local data | | Generate types after configuring bindings | Workers TypeScript |
Bindings and variables are not inherited automatically by named environments. Configure the required values for the environment being used, including its secrets. Binding names used in code must match configuration; the target resource's ID or name is a separate value.
Keep credentials out of committed variables and local secret files out of version control. Remote development can access real resources: verify the target rather than assuming that running locally isolates writes.