Repository navigation
Releases
Garrison 0.1.2
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, asgarrison doctordoes 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 invalue.aliases. garrison detectfinds the host's own firewall units and names them for
firewall_unitsof thehost-careprovider.- 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+l9U0OplCP6It 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 |
Garrison 0.1.1
Host care gets three fixes that the first weeks on a real server asked for.
It works with Stalwart 1.1.0, like 0.1.0.
What changed
- Firewall units of the host's own. A host whose own unit loads its
nftables rules got a firewall warning it could only silence by leaving the
check out. Name such units infirewall_unitsof thehost-careprovider;
the check then asks whether one of them runs. - The update check says what keeps it out. Where only root may read a
folder in/var/cache/dnf, as a dnf run under umask 077 leaves it, the
check names the repositories and thatchmod 755on their folders lets it
read them. - The update check follows the host. It asks the package manager again
within five minutes after packages are installed or removed or new metadata
is fetched, so a warning goes away soon after the update is installed.
The changelog
has the details.
Upgrading
From 0.1.0, garrison upgrade with the archive for your architecture and its
.minisig. Nothing in the configuration has to change; firewall_units is
optional. garrison install --rollback returns to 0.1.0; take
firewall_units out of the configuration first, as 0.1.0 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.1-x86_64.tar.gz -P RWSKAjJdo0lsYJJA64rSgwP6KeVtTEbgqB12xkoAVxzQd+l9U0OplCP6It must end with Trusted comment: garrison 0.1.1 x86_64 (or aarch64).
| Archive | SHA-256 |
|---|---|
garrison-0.1.1-x86_64.tar.gz |
60e82f8a0239af9898072961d83f31a404dc3e5505a33a1da0e31ab661ece657 |
garrison-0.1.1-aarch64.tar.gz |
87665ee48d547ad060bd8637bf1ff152c5c81054e9efdce38741bcd631da43c7 |
Garrison 0.1.0
The first release of Garrison, a console for everything around a Stalwart
mail server that Stalwart's own WebUI leaves to you. It works with Stalwart
1.1.0.
What is in it
- Pages for the dashboard, services, antivirus, the spam filter, attacks and
bans, backups, DNS and TLS, alerts and maintenance, and for deliveries, SMTP
sessions and the event history. - Checks of the host and of Stalwart that run every minute: units, pending
security updates, a disk forecast, certificates of every listener, DNS
records, blocklists, restic and borg repositories, test mail through the
server. - Messages to an ntfy topic, a webhook or a mailbox when a check fails and
when it is in order again. - An optional filter, off by default, that has Stalwart refuse or mark mail
with Office macros. - An installer with backup and rollback,
garrison setupfor a first
installation at a terminal,garrison doctorto check one, and an Ansible
role.
The changelog
has the full list.
Installing
Garrison needs Linux on x86_64 or aarch64 with systemd 247 and polkit 0.106 or
newer, nginx or another TLS proxy, and Stalwart 1.1.0 on the same host. Take
the archive for your architecture and its .minisig, check the signature
with the key from the README, then follow the
quick start.
Each archive comes with its signature, its checksum and a CycloneDX SBOM.
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.0-x86_64.tar.gz -P RWSKAjJdo0lsYJJA64rSgwP6KeVtTEbgqB12xkoAVxzQd+l9U0OplCP6It must end with Trusted comment: garrison 0.1.0 x86_64 (or aarch64).
| Archive | SHA-256 |
|---|---|
garrison-0.1.0-x86_64.tar.gz |
ad461f2d878ff734e7da11049d194afbb7f1307ae6cbce2398065e754ebdf398 |
garrison-0.1.0-aarch64.tar.gz |
f6b54b4a48d78b4fda6ac1529f052341d026684427ccb5db085bff60f86be39b |
Upgrades
garrison upgrade installs later releases once their signature checks out,
and garrison install --rollback returns to the one before. The changelog
names whatever an upgrade asks of you.