Environment check panel
The Environment check panel (right rail) tells you, for the selected scenario, whether you have what you need to launch it —before pressing play—. It’s the visual version of the environment check (doctor).
How to read it
Section titled “How to read it”At the top, the verdict: Ready to launch or Not ready, with the count of ok /
warnings / failures. Below, the results grouped by category:
- Repositories — each manifest exists and its repo is on disk.
- Tools — those required by the scenario’s stacks, with the detected version (or the
repo’s wrapper/
.venvthat satisfies them). - Micro requirements — what a specific micro declares apart from its stack.
- Docker — the daemon responds (only if the scenario needs it).
- Databases — TCP reachability of the selected external DBs.
- Credentials — each needed
${creds.x}has a value insettings.local.yml.
Warnings and failures
Section titled “Warnings and failures”A failure blocks the launch; a warning does not. Each result explains the reason
(for example “java is not on the PATH”, “the connection does not exist in the catalog”
or “no value in settings.local.yml”), so you know exactly what to fix.