Release candidate: 1.1.0-RC1

Sam Tuke Dec 18 2020 Share

This is an early release of the upcoming Lightmeter Control Center 1.1.0. It provides an opportunity to test the latest changes before the final release scheduled for next week. Please check old issues which affect you and are reported as fixed, as well as any brand new features, and also existing features for regressions.

Changes for testing

Web user interface
  1. The Web UI has been completely migrated to Vue.js. While it is designed to look the same, nearly all front-end code has changed.
Setup and configuration
  1. Support for reverse proxies added, tested with Nginx
  2. Support for hosting Lightmeter on URL subpaths added, e.g.
Log parsing
  1. New log file obfuscation script, for safely sharing private mail logs. This replaces the old bash scrip with a new Python one and fixes some issues
  2. Support hostnames which include hyphens (eg local-smtp-hostname)
  3. Support logs referring to Postfix address rewriting
  4. Fix “Empty Directory” error if mail.log has previously been imported and no rotated log files exist
  5. Support custom rotated log file name formatting e.g. mail.log-20000101.gz, understanding the date sequence from the name
Internationalisation and localisation
  1. New Web-based natural language selection menu (allows overriding the language detected from the browser user agent)
  2. Several improvements to the translation flow from backend string extraction to Weblate, and back to the repository

The full list of merge requests and commits is on GitLab.

How to test

The best way to test this Release Candidate is to use it as you normally use Control Center, in a non-critical environment. Known issues with this release are documented in the README.


Upgrading to an RC release is the same as for any other Control Center release.

Downgrading is also supported, but because downgrading depends upon features which may not yet be stable, successful downgrading should not be relied upon.

Testing specific features

Features which are user-facing can be easily tested using the Web-UI — see the associated GitLab issues for the expected behaviour and screenshots (sometimes) of how they are intended to look.

Where back-end changes affect a particular component (such as Internationalisation, parsing, etc.), deliberately using functionality which depends on those components provides good opportunities to test for regressions.

Reporting issues

Any found issues should be reported to GitLab, clearly stating the version number of the copy of Control Center that you’re using (e.g. 1.0.0-RC1).


Missing your favourite packaging system? Tell us in the comments.

Supported by

This release was funded through the NGI0 PET Fund, a fund established by NLnet with financial support from the European Commission’s Next Generation Internet programme, under the aegis of DG Communications Networks, Content and Technology under grant agreement No 825310.

Comments are closed.