Stage 3-5 server (military, expansion, social), web client for stages 1-2, ops/deploy
Built: units/research/training, movements (scan, raid, attack, takeover, reinforce, settle, transport), deterministic combat resolved in the event queue, reports, power/offline units, founding + conquest + incumbent sites; alliances, roles, diplomacy (24h pact cancel via events), messages, rankings; vanilla-JS phone-first client (auth, POP, map, alerts, settings, en/nb); systemd units, backup timer, DEPLOY.md, tools/admin.js. Tested: npm test 96/96 (fake clock, in-memory db, a few real-HTTP tests); client checked with headless Chromium screenshots only. NOT done: marketplace/transport trade, client screens for military/social, WebSocket push, bots/balance, e2e suite. All unit stats and costs are unbalanced first guesses. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Q2MJaQ5LXAHzGnTDgceT14
This commit is contained in:
parent
b56b13880e
commit
249818a7aa
111 changed files with 17472 additions and 13 deletions
14
deploy/upstream-backup.timer
Normal file
14
deploy/upstream-backup.timer
Normal file
|
|
@ -0,0 +1,14 @@
|
|||
# Daily snapshot at 04:15 (+ up to 10 min jitter). Persistent: a run missed while the container was off happens at
|
||||
# the next boot. Every 6 hours instead: OnCalendar=*-*-* 00/6:15:00 and raise --keep in upstream-backup.service.
|
||||
|
||||
[Unit]
|
||||
Description=Upstream - daily database snapshot
|
||||
|
||||
[Timer]
|
||||
OnCalendar=*-*-* 04:15:00
|
||||
RandomizedDelaySec=10min
|
||||
Persistent=true
|
||||
Unit=upstream-backup.service
|
||||
|
||||
[Install]
|
||||
WantedBy=timers.target
|
||||
Loading…
Add table
Add a link
Reference in a new issue