Getting started (plain English)

If you already have the two prerequisites installed — the .NET tools and Node.js — turning this on is two commands in two windows.

What you need first

• .NET (the tool that runs the backend "server" half)
• Node.js (the tool that runs the frontend "screen" half)

If neither is installed, that's a job for ../technical/getting-started.md, which has exact versions and links.

Turning it on

Window 1 — start the server:

dotnet run --project src/FleetMissionControl.Api

Window 2 — start the screen:

cd frontend
npm ci
npx ng serve --proxy-config proxy.conf.json

Then open http://localhost:4200 in a browser. That's the screen; it talks to the server automatically.

If something looks empty

That's usually correct, not broken. This cockpit only ever shows real data — if the usage-budget file, the repo list, or a machine's availability status doesn't exist yet on your setup, the matching panel just shows "unknown" or "none" instead of making something up. See OVERVIEW.md for exactly what it reads and what happens when a source is missing.

Checking your work before you commit it

There's a full set of automated checks (build, tests, lint, security scan) that run every time. Running them yourself first, described in ../technical/getting-started.md, catches most problems before they ever reach the shared checks.