Guides
This page applies the model to a real workflow. Open the guides overview
Daily workflow¶
This is the normal day-to-day rhythm once a repository is already set up. It is intentionally small: run, change one local value, inspect, validate, and debug only when needed.
When to use this page¶
Use this guide when:
- the repository is already initialized
- your local values mostly exist already
- you want the commands you repeat most often, not onboarding detail
Run your app¶
For most daily work, run is the default choice. It injects the resolved environment directly into the subprocess, so you usually do not need to materialize a dotenv file.
Change one local value¶
Use set when the contract stays the same and only your current local value changes.
Inspect the current state¶
Use inspect when you want to see the runtime view that envctl has actually resolved.
Validate before blaming the runtime¶
If something feels off, start here. A passing check tells you the contract-level state is valid before you debug the target tool.
Switch local context explicitly¶
Use a named profile when the same project needs a different local value set.
Keep the Git safety net healthy¶
Use this when your team relies on envctl-managed hooks and you want to confirm the local wrappers are still healthy.