Note: Version 1.9.1 is the latest version of this release — if you use binaries (not Docker) get them at the Gitlab registry. 1.9.1 includes a fix in the data cleanup process affecting large databases. More details on the issue here.
Note that Lightmeter is still in early development and intended for small scale deployments. Known issues are documented in README (and there’s one fewer thanks to a fix included below ?).
Fixes and conveniences
This release includes is a grab-bag of minor improvements, four of them requested by community members. Thanks a bunch to Oliver, Chris, and Stephen for spotting issues, sharing redacted logs, and testing the fixes. Keep it coming!
Peer network lift-off
Core development this cycle has focused on building an exciting new peer network system into Lightmeter, which is the foundation for upcoming Lightmeter 2.0 and future mailops automation features. We pre-announced these changes last week — go ahead and read that if you didn’t already (opens in a new tab).
As that announcement explains, today’s release introduces the sharing of certain data, and to prevent abuse requires accepting some Terms of Service. To avoid participating in that system (and the features which will use it), you can stay on Lightmeter 1.8.2, or wait until a future release which includes the option to disable it.
Allow admins to change their account e-mail and name via the command line
Allow logs to be compressed by bzip2 (.bz2) — thanks to Oliver Mueller for requesting the feature ?
To make more efficient use of disk space, logs older than 3 months are deleted from the Lightmeter database (no longer a “known issue”! ?).
Fix obtaining the most recent log lines from an existing workspace, which could cause duplicate connection stats
Introduce a filesystem watcher that identifies when a synchronization is finished, and in case the log files do not yet exist (not yet synchronized), controlcenter waits until files are completely synchronized, instead of exiting with an error.