tomevault-io Run Local
Start the local development environment using .NET Aspire.
Arguments
--backend-only— Skip the frontend dev server--no-dashboard— Skip opening the Aspire dashboard
Process
Step 1: Pre-flight
# Verify Docker is running (required for PostgreSQL, NATS, Valkey, Zitadel)
docker info > /dev/null 2>&1 || echo "ERROR: Docker is not running. Start Docker first."
# Verify .NET SDK
dotnet --version
Step 2: Start Aspire AppHost
cd src/SignalBeam.AppHost && dotnet run
The Aspire dashboard will be available at https://localhost:15888.
Step 3: Start Frontend (unless --backend-only)
In a separate terminal:
cd web && npm run dev
Frontend available at http://localhost:5173.
Ports
| Service | Port |
|---|---|
| Aspire Dashboard | 15888 |
| API Gateway | 5000 |
| Frontend (Vite) | 5173 |
| PostgreSQL | 5432 |
| NATS | 4222 |
| Valkey (Redis) | 6379 |
| Zitadel | 8080 |
Troubleshooting
- Port conflict: Check for running containers with
docker ps - Build failure: Run
dotnet build src/SignalBeam.slnfirst to see errors - Docker containers stuck: Run
docker compose downinsrc/SignalBeam.AppHost/to clean up
Post-Launch Verification
After the services start, optionally verify they're working using Playwright:
- Navigate to the Aspire dashboard at
https://localhost:15888usingmcp__playwright__browser_navigate - Take a snapshot with
mcp__playwright__browser_snapshotto confirm it loaded - Check
mcp__playwright__browser_console_messagesfor any errors
This is optional — only do it if the user asks to verify, or if there were recent issues with the local setup.
Related Skills
/smoke-testto verify the running app in the browser/run-teststo run tests after verifying locally/diagnoseif the local environment has issues
Converted and distributed by TomeVault — claim your Tome and manage your conversions.