Scenarios section

The Scenarios section is where you compose and operate your scenarios. On the side you have the list of scenarios; in the center, four views of the active scenario.

Create and edit

• New scenario opens the editor: name + the micros that make it up.
• Edit (top bar) returns to that editor to change its composition.
• Delete (item menu on the side) removes the scenario; asks for confirmation.

The four views

• Cards — one card per micro with its status, port, mode (native/container toggle) and actions (restart just that micro, open its configuration).
• Table — the same information in rows: status, start, endpoints, mode, actions (open configuration, view logs, copy URL). Each row’s toggles and links stay inline; the rest of the actions, in its menu.
• Graph — the who-calls-whom call graph, with each edge’s color according to its resolution (local, cloud or mock). You can zoom in, zoom out and fit to view.
• Dependencies — the local/cloud/mock selector per dependency, with the VPN notice if something points to the cloud. See Dependencies.

Operate the scenario

From the top bar:

• ▶ Start / ■ Stop — a single button that starts or stops depending on the state. It starts the infra, resolves ports, rewrites URLs and launches each micro; when stopping, it stops micros, containers and infra.
• Clean — terminates orphaned native processes and removes residual microlab-* containers. Useful if something got stuck.
• Prepare database — runs the post-migration steps (for example, seed) after the first migration.

Health at a glance

The scenario’s health summary (no issues / starting / with errors) is in the top bar and opens the Status tab of the dock. Each micro goes through the states Stopped → Starting → Healthy (or Unhealthy / Crashed). See Micro states.

Sharing

Exporting/importing a complete scenario is done from the side menu. See Share a scenario.