Skip to content

Courier v0.5.3 (beta)

Choose a tag to compare

View all tags
@rpycroft rpycroft released this 25 Oct 21:33
v0.5.3
2ccbdd3

Courier v0.5.3 (beta)

Courier 0.5.3 beta: the console can now be used from other computers on your network, with sign-in. A head or an office can send a notice from their own desk; nobody has to remote-desktop to the server any more.

What's new

  • Use the console from any computer on your network. Open https://<your server's name or address>:8445 in a browser and sign in. The first administrator account is still made on the server itself.
  • Optional: allow the console only from certain addresses. Settings > Access takes a list of addresses or ranges (such as 192.168.1.0/24). Leave it empty and any computer on your network can reach the sign-in page. The server itself can always open the console, so a mistake in the list cannot lock you out.
  • Updates now work out of the box on the beta. A new install checks the beta channel by itself, so Check for updates works without any token. (Alpha, the private development channel, is still a deliberate choice.)
  • Five wrong passwords lock that computer out of signing in for a minute, as before, now from any computer.

The computers running the RSJ Agent are not affected by any of this.

What has been seen working, and what has not

  • Seen working before this build (a lab server and PC, October 2026): sending a notice to a computer, having it shown and acknowledged, restarts, and upgrading with data kept (see the 0.5.2 notes).
  • Not yet proven on real machines: one person signed in on two computers, signing out and another person signing in, Active Directory groups on a real school domain, and automatic updates.
  • Known issue: a notice waiting for someone to sign in may not appear when they do. Send it again. This is being fixed in the RSJ Agent.
  • Not for emergencies. There is no promise that a notice reaches or interrupts anyone in time.

Help and documentation

Upgrading

On the Beta channel use Settings > Updates > Update now, or run the new installer over your current one; your accounts, history and settings are kept.

Download

File Description
CourierSetup.exe The whole Courier server -- install it on the Windows Server that will run Courier. The Courier module for your PCs is inside it and is handed to each PC by your own server. The RSJ Agent that runs the module on each PC is a separate install.

The two Source code links GitHub adds to every release hold only this repository's README and security policy, not the product.

SHA-256 checksum

Verify your download matches this before running it (PowerShell: Get-FileHash .\CourierSetup.exe):

File SHA-256
CourierSetup.exe 03BA537ACA0CEE6232E067BA3FE3F96B2F52AB5215A62659C22CA4EBF0840D47

Checked

The installer was scanned on VirusTotal before release:

About the beta

A beta build is newer than the public release, for trying new features before they reach everyone. It is tested by RSJ Software
but may still have rough edges. Install it over an existing Courier: your accounts, history and settings are kept.

To be offered betas, choose Beta under Settings -> Updates -> Update channel; you are also offered every public release as it
comes out. Tick Allow automatic updates there too if you want them installed without asking. To leave, choose Stable:
nothing older is ever installed, and the next public release arrives once it is newer than the beta you have.

What to expect when installing

Run the installer on the Windows Server that hosts Courier; it asks for administrator approval. The installer should name
RSJ Software Ltd as its publisher. If the publisher shows as unknown, do not run it -- tell us in an Issue on the main
repository. Take a copy of Courier's data folder first, with the Courier service stopped, as you would before any upgrade.

Help, questions and bug reports

Everything lives on the main repository, not here:

Assets 3
Loading