Manage the FedProspect dev stack: start, stop, restart, build, or check status of MySQL, .NET API, and Vite UI. Use when the user says 'start the stack', 'stop mysql', 'restart api', 'is anything running', 'build everything', 'spin up dev', 'tear down the stack', or any variation of managing dev services. Usage: /dev-stack <command> [service]
Manage the local development services (MySQL, C# API, Vite UI).
$ARGUMENTS = <command> [service]start, stop, restart, status, buildall (default), db, api, uipython fed_prospector.py <command> [service]
| Command | What It Does |
|---|---|
start [service] | Start service(s). Waits for each to be ready before returning |
stop [service] |
Graceful shutdown. Add --force for hard kill |
restart [service] | Stop + start |
status [service] | Check what's running and show URLs |
build [service] | Build API (dotnet build) and/or UI (npm run build) |
python fed_prospector.py start all # spin up everything
python fed_prospector.py status # check what's running
python fed_prospector.py restart api # bounce the API after code changes
python fed_prospector.py build api # build C# solution
python fed_prospector.py build ui # npm run build
python fed_prospector.py stop db --force # force-kill MySQL
| Service | Port | URL |
|---|---|---|
| MySQL | 3306 | — |
| API | 5056 | http://localhost:5056 |
| UI | 5173 | http://localhost:5173 |
| Problem | Fix |
|---|---|
| Port conflict | `netstat -ano |
| MySQL won't start | Check data dir exists at E:/mysql/data, check disk space, check error log |
| API won't start | Build first (build api), ensure MySQL is running |
| UI won't start | Ensure node_modules installed (cd ui && npm install) |
| Stop hangs | Use --force flag: python fed_prospector.py stop --force |