Releases and updates
How a new LogNorth version reaches your server, what the version tags mean, and how to run release candidates or pin a version.
LogNorth ships on a weekly train. New work runs as a release candidate for a week before your server gets it.
The weekly train
Section titled “The weekly train”Every Monday at 04:17 UTC:
- The candidate that ran for 6 days or more becomes the stable release.
v0.29.0-rc.2becomesv0.29.0, from the same commit. - When there are new changes, they become the next candidate:
v0.30.0-rc.1.
A candidate that changes nothing you can see, such as docs or build settings, stays a candidate. When a candidate needs a fix, the next candidate replaces it and waits its own 6 days.
Your server updates each night at 05:30 UTC, after a backup of its database. A new release reaches it at the first update after the release is out.
Version names
Section titled “Version names”| Version | What it is |
|---|---|
v0.29.0-rc.1, v0.29.0-rc.2 |
Release candidates of 0.29.0. The number after rc. counts them. |
v0.29.0 |
The stable release, from the commit of the last candidate. |
Each version is a Docker image with the same name, without the v: karloscodes/lognorth:0.29.0-rc.2. Two more tags move with the train:
| Image tag | Holds | Who follows it |
|---|---|---|
latest |
The newest stable release | Every install, unless you change it |
rc |
The newest release candidate | Servers that run candidates |
The same images are at ghcr.io/karloscodes/lognorth-releases. Candidates show as pre-releases on the releases page.
Run the release candidates
Section titled “Run the release candidates”To get each candidate the night after it comes out, point the server at rc. Run this from your computer, with the Chasen CLI logged in to the server:
chasen deploy karloscodes/lognorth:rc --auto-updateThe domain, the data, and the settings stay. LogNorth updates to the newest candidate now, and each night after that.
To go back to the stable releases:
chasen deploy karloscodes/lognorth:latest --auto-updateThe install line also puts the server back on latest.
Pin a version
Section titled “Pin a version”To stay on one version, deploy it and turn off the nightly update:
chasen deploy karloscodes/lognorth:0.28.0 --no-auto-updateTo roll back the last update, chasen -a lognorth rollback is faster. It keeps the version before on the server.