Audience landing pages, steadier package builds, and upgrades that keep every service running.
Added
- A landing page and pages for each audience (#379, [#380]). With
LANDING_PAGE=1,/becomes a landing page and/for/educators,/for/researchers,/for/investigators,/for/operations,/for/writersand/for/developersdescribe OpenChronology for each audience, with example timelines (LANDING_EXAMPLES,LANDING_EXAMPLES_<AUDIENCE>), an optional click-to-load video (LANDING_VIDEO,LANDING_VIDEO_<AUDIENCE>) and copy an operator can override (LANDING_CONTENT_DIR). The timeline browser is always at/explore. Off by default: servers that don't set it keep/as the timeline browser.foris now a reserved username. See Landing page in the administration docs.
Fixed
- Upgrades leave no service stopped (#371, [#373], [#374], [#375]). After an upgrade,
openchronology-migraterestarts the mail worker and the syslog and journald importers when they are enabled (Debian, Ubuntu, RPM, FreeBSD, Homebrew and Windows); releases up to 0.12.1 left them stopped until started by hand. - Package builds no longer hang on a stalled mirror (#367, [#368], [#369], [#370]). apt, dnf and curl in the builds retry and give up on a stall, each build step has its own time limit, and the Linux package builds use a cached, checksum-verified Node.js tarball instead of downloading it inside Docker.
Changed
- The publicity videos moved to their own repository (#378); this repository holds only the app.
Upgrading
Install the new package and run openchronology-migrate as usual. Nothing in the database changes. To turn on the landing page, add LANDING_PAGE=1 (and any LANDING_* settings) to the server's environment and restart it.
