Updates
This page is also in the Courier wiki: https://github.com/rsjsoftwareltd/courier/wiki/Updates
Courier does not update itself unless you ask it to. This page covers how to move to a newer version, and what the Updates tab in Settings does.
The simple way: run the newer installer #
Download the newer CourierSetup.exe from the Releases page, check its checksum as in Getting Started, and run it over the existing install. It stops the Courier service, replaces the program files and starts it again. Your data folder is not touched. Take a copy of it first (Backup and Restore).
The Updates tab #
General Settings -> Updates is for administrators. It shows the version installed and lets you:
- Check for updates -- look for a newer published version and show its release notes.
- Verify & prepare installer and Download verified installer -- download the installer, check it against the checksum published with the release, and hand it to you to run yourself.
- Update now -- do the same, then run the installer for you. The Courier service restarts for a minute or two and the page reconnects by itself. Recent updates lists every result, including a failed one and why.
- Allow automatic updates -- off unless you turn it on. Once a night, at 03:00, Courier looks for a newer version and installs it by itself, once per version.
Whichever way it happens, Courier will not install an installer whose checksum does not match the one published with the release, and will not install an older version than the one running.
Update channel #
General Settings -> Updates -> Update channel chooses where the check looks:
- Stable -- public releases. It becomes the default when the first public release is out.
- Beta (default for now) -- try new features before the public release. Beta builds are tested by RSJ Software but may still have rough edges. You are also offered every public release as it comes out. Switching back to Stable never installs an older version: the server stays on the beta it has until a newer public release arrives. Beta needs no token.
- Alpha -- private development builds. These need a read-only GitHub token from RSJ Software.
Where updates are read from #
Today the tab reads from a private build channel and needs a read-only token, so with a public release run the installer by hand as above. When Courier's updates come from the public Releases page the token goes away, and this page will say so. Update now and automatic updates have not yet been proven on a real server.
What it contacts #
Checking for and downloading updates is the only time Courier contacts the internet, and only when you ask it to or turn automatic updates on. Courier sends nothing about you to RSJ Software.