Update Healer Man server

This commit is contained in:
phenom committed 2026-09-19 14:33:15 -04:00
1 parent a05a79eb83
commit f8314e7de1
14 files changed
+529 -108

No files matched your search

+14 -6
View File
@@ -199,6 +199,13 @@ job returns as failed after restart, while any job with a complete
unless the server has enough spare CPU for multiple full combat sweeps. All
Balance Lab routes independently require a server-authorized GM account.
Balance Lab's one-shot `vite-node` workers run in the dedicated `balance-lab`
Vite mode, which disables the public directory and ignores all filesystem-watch
paths. This is required for parallel sweeps: without it, concurrent workers can
exhaust Linux's file-watcher limit while scanning the shipped asset tree and
fail immediately with `ENOSPC`. Do not use a larger inotify allowance as the
primary fix; deploy the current runtime configuration.
After saving the YAML, restart the TrueNAS app and watch its startup log for a
line beginning with `Python 3.`. Reopen Balance Lab; the setup panel must show
**Server runtime ready** before **Run on server** becomes available. The server
@@ -224,12 +231,13 @@ schema-compatible with Healer Man and must not be copied over the new one.
## Update workflow
For a code update that includes a new APK, the visual workflow in
`RELEASE_RUNBOOK.md` is recommended. For a manual release, choose the next
version first. The example below upgrades `0.1.2` to `0.1.3`; replace `1003` if
it is not greater than every prior Android `versionCode`. Then run these
commands in **Windows PowerShell**
on the development PC. Stop if any test or build fails:
The visual release manager described in `RELEASE_RUNBOOK.md` defaults to **Git
+ TrueNAS only**, which commits and pushes a server update without changing the
Android version or publishing an APK. Clear that toggle when a code update also
requires a new APK. For a manual APK release, choose the next version first.
The example below upgrades `0.1.2` to `0.1.3`; replace `1003` if it is not
greater than every prior Android `versionCode`. Then run these commands in
**Windows PowerShell** on the development PC. Stop if any test or build fails:
```powershell
Set-Location F:\Projects\HealerMan