Skip to content

Garrison 0.1.2

Latest

Choose a tag to compare

@relative23 relative23 released this 13 Nov 13:37
· 425 commits to main since this release

Stalwart's sign-in page is now checked all the time, and the metric history
takes a fifth of the space. It works with Stalwart 1.1.0, like 0.1.1.

What changed

  • The sign-in page is checked all the time. The new check sign-in
    loads Stalwart's sign-in page under the issuer's name every five minutes,
    with every script and style sheet it names, as garrison doctor does when
    it is called. A page that does not answer, is not Stalwart's or cannot load
    its files is a failure, and the notifications report it within minutes:
    after a Stalwart release that loads files the proxy does not pass, nobody
    can sign in.
  • The metric history takes a fifth of the space. It keeps every minute of
    the last eight days and ten-minute values before them, so the 30-day and
    90-day views show the same and load faster. With every check, 90 days take
    about 48 MiB instead of about 250.
  • Observation ids are documented and kept. The page
    observation ids
    lists the id of every observation, for scripts that read Garrison's status.
    A release that renames one says so there and in the changelog, and for one
    more release the observation also carries its old id in value.aliases.
  • garrison detect finds the host's own firewall units and names them for
    firewall_units of the host-care provider.
  • The switch rows start hidden. Each user turns them on in Garrison's
    settings; a setting saved before keeps its value.
  • The logo names only Garrison.

The installation guide now names the memory and disk Garrison needs. Inside,
the checks moved out of the collector into crates of their own. The
changelog
has the details.

Upgrading

From 0.1.1 or 0.1.0, garrison upgrade with the archive for your
architecture and its .minisig. The configuration stays valid. For the new
check, add this entry to /etc/garrison/garrison.toml:

[[providers]]
type = "sign-in"

The first collection run after the upgrade rebuilds an index of the metric
history, which takes about a second, and the history is thinned within some
80 minutes after that.

A rollback to 0.1.1 needs garrison install --rollback --restore-state:
0.1.1 cannot write the changed metric history, so a plain rollback stops
before it changes anything. The data recorded since the upgrade is then lost.
Take the sign-in entry out of the configuration first, as 0.1.1 does not
know it.

Checking a download

Both archives were built twice by the release workflow and once on the
maintainer's machine, with byte-identical results, and GitHub's build
attestation names the commit they come from. Check the signature before you
unpack an archive:

minisign -Vm garrison-0.1.2-x86_64.tar.gz -P RWSKAjJdo0lsYJJA64rSgwP6KeVtTEbgqB12xkoAVxzQd+l9U0OplCP6

It must end with Trusted comment: garrison 0.1.2 x86_64 (or aarch64).

Archive SHA-256
garrison-0.1.2-x86_64.tar.gz 948019970bb332b23457aa5b34756addde0fd22623a5bebb0abb35a063190228
garrison-0.1.2-aarch64.tar.gz 9a06ab037774b3335ffbb69595173762fa48e17254099442b00ed216f7aa07bd