Production deployment (canonical)

Mission: successful production on all Grudge Studio hosts — no parallel redesigns.
Admin shell: Dev Tool embeds production Forge/Coder and previews live clients — see Admin architecture.

ONE TRUTH hosts

Never use api.grudge-studio.com for new wiring (deprecated split-brain).

Docs site pages (all from docs/): Home · Systems & APIs · Admin architecture · ONE TRUTH · Databases · sharing · backups · API reference · Object storage · AI · D1 · R2 · Stream · Quickstart · CLI.

Database backups (ops)

# Player SSOT — parallel logical dump (requires DATABASE_URL + npm i -D pg)
$env:DATABASE_URL = "<Railway Postgres public URL>"
npm run backup:postgres
# → backups/<stamp>/meta.json + tables/*.jsonl.gz   (gitignored)

# Optional full custom dump via Docker
npm run backup:postgres -- --pg-dump

Full map (sharing scopes, RPO, D1/R2 recovery, PlanetScale-inspired growth path):
Databases · sharing · backups.

Secrets (Windows Credential Vault + CI)

# Import production block (never commit .env with real secrets)
npm run secret:import -- "$env:USERPROFILE\secrets\grudge-production.env"
npm run secret:verify

See production-config.md.

GitHub best practices (this repo)

Pages base path

docs/_config.yml:

url: "https://grudge-warlords.github.io"
baseurl: "/grudge-dev-tool"

Repo Settings → Pages → GitHub Actions (not branch deploy).

Desktop Forge release (package v1.0.1 — check Releases for latest tag)

npm ci --legacy-peer-deps
npm run typecheck
npm run package:ci      # NSIS installer → release/
# or tagged release (CI + local artifact):
git tag v1.0.1 && git push origin v1.0.1
# prefer: npm run publish:manual after package

Installer embeds: Electron main/renderer, Three.js, glTF-Transform, Puter, keytar, FBX2glTF tool resource.
Forge tab loads live forge.grudge-studio.com (not a bundled second editor).

Latest: GitHub Releases

glTF / convert (production bar)

Skills: grudge-asset-convert · forge-editor · grudge-d1-r2.

Multiverse deploy (live game with own Railway)

Rule: each multiplayer game gets its own Railway when it needs rooms — do not piggyback Carrier / gameopen-production for Multiverse.

CLI (cli/)

cd cli && npm install && npm run build && npm install -g .
grudge-dev setup
grudge-dev doctor

AI workers & GRUDACHAIN Ollama

Auto-start behavior (Forge v0.9.1+)

1. App open → ollama.ensureRunning({ reason: "app-open" })
   • Docker container GRUDACHAIN with -p 11434:11434 + volume grudachain-ollama
   • Recreates container if host ports were never published
   • Falls back to native ollama serve
2. Admin sign-in (grudachain / molochdadev) → agentic ensure (prefer Ollama, pull default model if empty)
3. Status bar: OLLAMA · AGENTIC when models are available

Preference: Settings → AI → auto | ollama | cloudflare.
auto uses Ollama when localhost:11434 is healthy.

UUID / Three.js / Forge

Multi-era assets (production organization)

Store tab categories in src/shared/fleetGames.ts → STORE_CATEGORIES map ObjectStore paths.
Upload: convert → recognize era → correct R2 prefix → manifest with era field → D1.
Docs: ObjectStore docs/ERA-ASSET-TAXONOMY.md + asset-packs-canonical.

Account / cloud best practices

1. One human → one Grudge ID (id.grudge-studio.com).
2. JWT in fleet keys: grudge_auth_token, grudge_session_token, sso_token.
3. Characters + account bag on Railway (/api/characters, /api/account).
4. Puter KV/FS = cache / user-pays only — never sole SSOT.
5. Admin UX gate is not security — Worker/API enforce privileges.

Verify production

npm run fleet:probe
# or
grudge-dev doctor

Expect core hosts live; Ollama may show unknown when not installed (optional).

Related surfaces