Files
dingoandClaude Sonnet 5 5df2f1b681 Merge control portal work from RPGTheory/aeternalis-portal
RPGTheory/aeternalis-portal had diverged from this repo (the git/CI/CD
copy) with an in-progress control portal feature that was never synced
back here, so none of it had gone through CI or been deployed:

- New site/game/control routing split: index.html becomes a world
  directory landing page (site.ts), game.html is the renamed former
  index.html (main.ts), control.html is a new admin panel
  (control.ts, portal-shared.ts, portal.css).
- Server: new internal/store/portal.go (character/world registry,
  command queue, admin grants) and internal/transport/control.go
  (portal API routes), plus a new internal/gitops package that lets
  the portal provision new worlds via a GitOps repo commit.
- game.World gains BornAt/DiedAt/DeathReason and an operator Control()
  path (close/open admissions, awaken boss, end world, per-character
  rename/heal/unstuck/retire); death no longer reuses the same
  character id on rejoin, matching the "new life" permadeath model in
  Plan.md rather than the old bypass-prevention test's expectations.
- deploy/: new control-egress network policy and portal/control
  values (admin role, GitOps repo/branch/values file/CIDRs).
- New e2e coverage: tests/portal.spec.ts, tools/capture-world.mjs.

Verified this repo's own independent commits (800ms movement-staleness
window, 20s boss-attack poll, SRS/TLS deploy values, ubuntu-22.04
runner pin, DOCKER_HOST fix) were already present in the portal copy
before merging, so nothing here regresses them. `tsc --noEmit`, the
vite client build, and the protocol contract check all pass; no go.mod
changes. Could not run `go build`/`go test` locally (no Go toolchain
on PATH, Docker daemon not running) — every new/changed Go symbol was
manually cross-referenced and resolves, but this should still be built
and tested in CI before merging to master.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-06 11:08:44 -04:00

56 lines
1.4 KiB
YAML

image:
repository: harbor.example.invalid/games/aeternalis
tag: bootstrap
digest: ""
imagePullSecrets:
- name: harbor-pull
existingSecret: aeternalis-runtime
portal:
host: ""
primaryWorld: world-001
control:
adminRole: aeternalis-admin
existingSecret: ""
gitopsRepository: ""
gitopsBranch: master
gitopsValuesFile: deploy/values-srs.yaml
gitopsCIDRs: []
databaseCA:
configMap: ""
externalDatabase:
name: pg-forge-01
address: ""
ingress:
className: nginx
tlsSecret: aeternalis-tls
clusterIssuer: ""
worlds:
- id: world-001
seed: "734291"
host: world-001.aeternalis.example.invalid
- id: world-002
seed: "829312"
host: world-002.aeternalis.example.invalid
- id: world-003
seed: "942731"
host: world-003.aeternalis.example.invalid
- id: world-004
seed: "1037412"
host: world-004.aeternalis.example.invalid
- id: world-005
seed: "1123491"
host: world-005.aeternalis.example.invalid
resources:
requests: { cpu: "500m", memory: "256Mi" }
limits: { cpu: "2", memory: "1Gi" }
networkPolicy:
enabled: true
ingressNamespace: ingress-nginx
# Node addresses for ingress controllers using host networking.
ingressCIDRs: []
# Explicitly set actual database and OIDC provider IP ranges before deployment.
databaseCIDRs: []
identityCIDRs: []
# Kube-dns defaults; adjust for clusters using NodeLocal DNSCache.
dnsNamespace: kube-system