BlueGit

timfa questward

Files

questward / deploy
README.md

Production deploy (systemd)

Behaviour

On every service start (clean midnight restart, crash, or power loss recovery):

1. git fetch + git reset --hard origin/<branch> 2. git pull --ff-only 3. npm install --omit=dev 4. start node --experimental-sqlite server/src/index.js

Pull-on-crash is intentional so a fixed commit on origin can recover a bad build.

Player-facing midnight schedule (3-hour countdown toast) still lives in the Node process: it detects that origin is ahead, warns players, then exits cleanly so systemd runs the update script above.

Install on the host

cd /srv/questward/current   # or your clone
sudo ./deploy/install-service.sh

Optional env overrides:

VariableDefault
QUESTWARD_REPOparent of deploy/
QUESTWARD_USERquestward
QUESTWARD_GIT_BRANCHmaster
QUESTWARD_AUTH_CLIENT_SECRET(unset — stub auth)

See root README.md for OAuth / auth.timfalken.com setup.

TILE_MMO_* env vars are still accepted as fallbacks for older installs.

Manual ops

sudo systemctl restart questward
journalctl -u questward -f

Disable the in-process schedule locally with QUESTWARD_DEPLOY_SCHEDULER=0.