Local Development¶
The repository includes a devcontainer and an Aspire AppHost that starts every service together.
Start Everything¶
- Open the repository in its devcontainer.
- Install
node_modulesinsrc/chronicle/uiand the Scenario Builder's insrc/scenario-builder/uiandsrc/scenario-builder/agent. On the devcontainer's mount,npm installcan fail withENOTDIR; the Scenario Builder README shows the workaround. - Press F5 in VS Code ("Aspire: RangerAI (all services)"), or run
aspire runfrom the repository root. - Watch logs and status in the Aspire dashboard at http://localhost:15180.
| Service | URL | What |
|---|---|---|
chronicle-api |
http://localhost:5285 | Chronicle API: publish and subscribe to Chronicles (Swagger at /swagger) |
chronicle-ui |
http://localhost:4320 | Chronicle Angular UI: lists events and opens each one (proxies /api to :5285) |
scenario-builder-api |
http://localhost:5280 | Scenario Builder .NET API |
scenario-builder-ui |
http://localhost:4310 | Scenario Builder Angular UI (proxies /api to :5280) |
Ollama, LiteLLM and the stand-in fake model server (:5299) are started separately. See Scenario Builder › Models.
Tests¶
dotnet test src/RangerAI.slnx
The Chronicle tests also check that the generated JSON Schemas and the sample in src/chronicle are current. After
changing a Chronicle type, regenerate them with CHRONICLE_UPDATE=1 dotnet test src/chronicle/Chronicle.Tests and
review the diff.
Adding a Project¶
New parts are added to the AppHost in src/apphost. See its README for .NET, Node and Python projects.
These Docs¶
The site is built with Material for MkDocs. Run mkdocs serve from the repository root to preview it at http://localhost:8000. See contributing.md.