A .NET Blazor application — a knowledge graph and AI assistant over Wookieepedia data. Aspire orchestrates the services locally and produces the deploy artifact, but Aspire is the dev/build harness, not the app.
- Ask AI — A streaming chat agent with chart, graph, timeline, table, infobox, and markdown render tools. Every value is sourced from a tool call; nothing is fabricated.
- Semantic search — Vector search over Wookieepedia article passages, available standalone and inside the agent.
- Knowledge graph — Entities and relationships extracted deterministically from infobox data, with temporal facets across six semantic dimensions and two calendar systems (galactic BBY/ABY + real-world CE).
- Holocron — An async LLM pass that proposes annotations and refines temporal bounds on top of the deterministic graph, gated and checkpoint-resumable.
- Galaxy map — Drill from regions to planets, plus an animated timeline mode with territory control and faction overlays.
- Graph explorer, timeline browser, data tables, AI-generated character timelines.
The authoritative description lives in src/StarWarsData.AppHost/Program.cs — the AppHost composes:
| Resource | Role |
|---|---|
frontend |
Blazor Interactive Server UI (MudBlazor). Public; authenticates via Keycloak OIDC. |
apiservice |
ASP.NET Core API. Hosts the AI agent (Microsoft.Extensions.AI + Microsoft.Agents.AI, streamed via AGUI). Internal-only — user identity forwarded from the frontend. |
admin |
Blazor admin app. ETL triggers (exposed as Aspire HTTP commands) and Hangfire recurring jobs. |
mongodb |
Either an external MongoDB server (default) or an Aspire-managed mongodb-atlas-local container (opt-in via use-local-mongo, see ADR-010). |
mongodb-mcp |
MongoDB MCP server sidecar — the agent issues read-only queries through it. |
mongodb-migrations |
Run-once container that applies schema/index migrations via mongosh. |
snapshot-restore |
Dev-only run-once resource that restores a prod snapshot into the local Mongo container. |
See ONBOARDING.md.
A push to main triggers .github/workflows/deploy.yml:
- GitVersion → build → unit tests.
aspire do pushbuilds container images forapiservice,admin,frontend, andmongodb-migrations, pushing toghcr.io/pjmagee/starwars-datawith both a semver tag andlatest.aspire publish -e Productionemits adocker-compose.yamland an unfilled.env.Productiontemplate. CI never sees secrets — the artifact is grep-scanned for OpenAI keys and Mongo passwords before upload, and the build fails if anything leaks.- The artifact is uploaded to the GitHub Release; the deploy host materialises real values into
.env.Productionfrom its own secret store and runsdocker compose --env-file .env.Production up -d.
Full contract: specs/017-aspire-publish-deploy-workflow/spec.md.
Anything authoritative — projects, conventions, ETL phases, MongoDB collection namespaces, ADRs, design docs — lives in CLAUDE.md and eng/. This README intentionally stops where the drift-prone facts start.
Built and maintained as a solo effort. Significant time and cost go into running AI models — Claude (Anthropic) for development, OpenAI for the in-app assistant and embeddings.
