Gately v0.5.5.1 released

October 21, 2026

This release resolves issue #8: module runtime logs used to live in memory only, so they were gone after restarting the container or upgrading.

Persistent runtime logs

System and module logs are written to logs/ in the configuration directory by default, one JSON Lines file per source, so the System logs page and every module page still show earlier logs after a restart or upgrade;
New entries are written in batches at most 1 second later, and nothing is written while idle. Each file is limited to 2 MB by default, then rotated with one previous file kept;
Settings → Network & Runtime → Runtime parameters adds a "Persist logs" switch and a "Log file limit", effective immediately. When off, logs stay in memory only, as before;
Clearing a module's logs in the UI also deletes its files. Configuration backups do not include logs.

The audit log has always been stored in audit.log and is unchanged. See Configuration · Runtime logs.

From v0.5.5: Linux binary installs upgrade directly from the About page; Docker pulls the new image and recreates the container; fnOS installs the new .fpk from the App Center; OpenWrt installs the new .ipk / .apk.
"Check for updates" in v0.5.4 and earlier only understands three-part version numbers and will not offer v0.5.5.1. Use "Upload upgrade package" on the About page with the .tar.gz for your platform from the Release, or upgrade to v0.5.5 first.
With Docker, logs are in the mounted configuration directory, for example ./gately-data/logs/.