The workspace and the .microlab/ folder
MicroLab stores two things in different places: your repositories (the workspace)
and its own configuration (the .microlab/ folder).
Workspace
Section titled “Workspace”It’s the base folder that contains your micros’ repositories. By default it’s the folder that contains the app itself; if your repos are elsewhere, you point to it in Settings → Paths → Workspace. Manifests store each repo’s path relative to this workspace, so they are portable across machines.
The .microlab/ folder
Section titled “The .microlab/ folder”It’s where MicroLab’s configuration for a project lives. What it contains:
| Path | What it is | Git? |
|---|---|---|
scenarios/*.yml | The scenarios | Versionable |
micros/ (manifests) | Each micro’s description | Versionable |
mocks/<service>.json | The mock catalog per service | Versionable |
databases.yml | The database connections catalog | Versionable |
settings.local.yml | Local config and credentials for this machine | Outside Git |
.runtime/ | Runtime state (control server, logs, entitlements, consent, temporary overrides) | Outside Git |
The idea: what belongs to the project or team (scenarios, manifests, mocks) is
versioned and shared; what belongs to your machine (absolute paths, secrets,
ephemeral state) stays in settings.local.yml and .runtime/, outside version control.
Credentials and ${creds.x}
Section titled “Credentials and ${creds.x}”Secrets never go in cleartext in a versioned file. They are stored in settings.local.yml
(editable in Settings → Credentials) and referenced in manifests, dependencies and
databases as ${creds.<key>}. MicroLab resolves them at startup.