dune-tools/character-builder
Vantz Stockwell 52d2abd16b Keep the three subtrees side-by-side in a class skill tree
- Skill tree panel now uses flex-wrap: nowrap so the 3 subtrees always sit
  inline matching the source layout. If the panel column is narrower than
  the trio (e.g. on mid-width screens with the summary sidebar visible),
  the row scrolls horizontally rather than stacking.
- Wrap max-width grows from 1560 to 1680px to give the builder column more
  room — the widest class layout (5+3+3 col subtrees) needs ~1160px of
  horizontal space and now fits comfortably without scroll on common
  desktop widths.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-23 08:25:01 -04:00
..
backend Add Dune Awakening character builder + initial project scaffolding 2026-05-23 07:30:37 -04:00
data Skill tree: subtrees, loadout slots, label fix 2026-05-23 08:21:09 -04:00
frontend Keep the three subtrees side-by-side in a class skill tree 2026-05-23 08:25:01 -04:00
scripts Skill tree: subtrees, loadout slots, label fix 2026-05-23 08:21:09 -04:00
.dockerignore Add Dune Awakening character builder + initial project scaffolding 2026-05-23 07:30:37 -04:00
docker-compose.yml Use external port 9002 instead of 8080 2026-05-23 07:30:55 -04:00
Dockerfile Add Dune Awakening character builder + initial project scaffolding 2026-05-23 07:30:37 -04:00
README.md Use external port 9002 instead of 8080 2026-05-23 07:30:55 -04:00

Dune Awakening — Character Builder

Plan your character across House, Class, Character XP, Specializations, Faction Standing, and Skill Trees. Shareable via short link.

Stack

  • Frontend: Vue 3 + Vite + TypeScript
  • Backend: NestJS (Node 22, TypeScript)
  • Storage: Valkey (Redis-compatible) for build sharing
  • Data: extracted from ../sample-data/*.html into ./data/*.json via scripts/extract.py

Two containers: app (NestJS serving the SPA + API) and valkey. Wire-up in docker-compose.yml.

Run

docker compose up --build

Then open http://localhost:9002.

Update data

If you save new HTML snapshots into ../sample-data/, re-run the extractor:

uv run python3 scripts/extract.py

This regenerates ./data/*.json, which the container picks up on next build.

API

  • POST /api/builds — body is a build payload (any JSON ≤16 KB). Returns { code } (8-char URL-safe id).
  • GET /api/builds/:code — returns { code, build }.
  • GET /api/data/:file — serves the static JSON tables (allow-listed).

Builds are stored in Valkey with a rolling 1-year TTL (refreshed on each fetch), so popular shared builds don't expire.

Dev (without Docker)

In two terminals:

# backend
cd backend && npm install && VALKEY_URL=redis://localhost:6379 npm run start:dev

# frontend
cd frontend && npm install && npm run dev

The Vite dev server proxies /api/* to localhost:3000.