Release server: installations, releases and update requests
Running the central release server: adding installations and issuing registration codes, uploading and revoking signed releases, requesting an update for an installation, and the server settings.
The release server is the central installation that serves releases to the other installations. Here you keep track of installations, issue registration codes, upload and revoke releases and request updates for individual installations. The screen is only useful once the release-server role is switched on.
Adding an installation and a registration code
- Open System → Release server.
- If not yet enabled, switch on Release-server role in the settings and save.
- Click Add installation (plus icon).
- Fill in Name, Domain and Client company, choose Operating model (central, island, hosted) and Release channel, set Automatic updates allowed and Status, then save.
- In the installation's row click the key icon (Issue registration code) and confirm.
- Hand the installation ID and the code to the operator: the code is shown only once and is valid for 7 days.
Uploading and revoking a release, requesting an update
- Click Upload a signed release (upload icon) and provide Package (.zip), Manifest (.json), Signature file (.sig) and Signing key ID. Without package and manifest: "Upload the package and the manifest."
- In the row of a faulty release click the ban icon (Revoke release) and fill in Reason. Installations then show this version as revoked.
- To request an update, click the paper-plane icon (Request update) in an installation's row and enter Target version, Request (prepare or install) and, if needed, Note. For an unpublished version: "This version is not published."
The installation picks up the request at its next automatic check. It only installs if accepting central installation requests is enabled there; otherwise it only prepares and waits for approval.
Settings
| Field | Meaning |
|---|---|
| Release-server role | switches the role on; the master key is generated the first time |
| Release archive | Google Drive (account and private folder), local storage or an HTTPS address with an auth header |
| Cached releases, Cache size limit (MB) | 1–20 releases, at least 16 MB |
| Allow updates for expired subscriptions; Allow updates for plans without the update feature | licence exceptions |
| Security releases are always allowed (except disabled installations) | security override |
| Download token lifetime (s); Download token uses | 60–3600 seconds; 1–10 uses |
Example
The central server adds the installation "Example plc – island" with the island model on the Stable channel and issues a registration code. The operator registers in Example plc's Update Manager. A week later the central server requests version 1.4.2 in prepare mode; Example plc's installation prepares it overnight and the administrator approves it in the morning.