Environment check (doctor)
The environment check (or doctor) answers “do I have what I need to launch this scenario?” before you press play, instead of discovering it with a failure mid-launch.
It’s available as a panel in the app (Environment check, right rail) and as a command
(microlab doctor [scenario]).
What it checks
Section titled “What it checks”The report is grouped by category:
- Repositories — each micro’s manifest exists and its repo is on disk.
- Tools — those required by the scenario’s stacks (
java+maven,node+npm,npxfor Angular,python…), probed with their version command. The repo’s wrapper (mvnw) or the.venvsatisfy the requirement without requiring the global tool. - Micro requirements — what a specific micro declares it needs beyond its stack (another tool, a path that must exist…).
- Docker — the daemon responds, only if the scenario launches infra or runs some micro in a container.
- Databases — TCP reachability of the selected external databases.
- Credentials — each
${creds.x}the startup will need has a value insettings.local.yml.
Warnings vs failures
Section titled “Warnings vs failures”- A failure blocks: something essential is missing.
- A warning does not block: it’s something optional or recoverable.
In the CLI, microlab doctor exits with code 0 if there are no failures and 1 if
there are, which makes it useful as a pre-gate in a script.