In the console
Administrators see the new release, what it fixes and the commands to run for their server. A release with security fixes also shows a banner and sends one email.
Releases
Every release, and what it fixes.
Your Fadenstack server reads this list once a day and tells its administrators when a new release is out. Nothing installs itself: you choose when to upgrade.
Loading the releases…
Release notes are written in English.
How your server hears of it
A new release, without anyone having to look.
Once a day the server and the command line tool read this list. Nothing about your server is sent: the list is fetched like any file and compared on the server.
On the command line
faden says so after a command, at most once a day. Upgrading takes two commands:
pipx upgrade fadenstack
faden upgradeSigned
Your server accepts only a list signed by the Fadenstack project, and never an older one than it has, so a changed list can neither hide a release nor invent one.
Without internet access
Put index.json and index.json.sig on a web server in your network and point the check at the copy, upload the two files in the console, or switch the check off.