Updating a venue
The venue server is updated with a button, without a terminal. The publisher releases a version on the platform; the venue sees it appear and the administrator chooses when to apply it. The same screen exists in the online back office, venue by venue.
The registers update separately, on their own: see Register updates.
The screen
Section titled “The screen”The Serveur de la salle (Venue server) tab (the other tab, Postes de caisse (Register devices), lists the registers) shows the Version du serveur (Server version) card: Version en place (Installed version), Plateforme (Platform), Service de mise à jour (Update service), Fenêtre de nuit (Night window) and Arrêt annoncé (Announced downtime), with a status badge:
| Badge | What it means |
|---|---|
| À jour (Up to date) | The venue has the latest released version. |
| Mise à jour disponible (Update available) | A Mise à jour disponible : X.Y.Z card appears, with its Notes de version (Release notes). |
| Version trop ancienne (Version too old) | The platform no longer accepts uploads from this version: update. Uploads wait, nothing is lost. |
| Programmée (Scheduled), Demandée (Requested), Reportée (Postponed), En cours (In progress) | An update is on its way (see below). |
| Aucune version publiée (No version released) / Aucune version annoncée (No version announced) | Nothing to install for now (no version released, or venue not yet linked or confirmed). |
| Service de mise à jour muet (Update service silent) | The service that installs versions on the PC no longer responds: restart the venue PC, otherwise call the publisher. |
| Pas de mise à jour par bouton (No button updates) | This server was not installed with the installation command: it does not have the update service. |
Update
Section titled “Update”- Read the Notes de version (Release notes) on the Mise à jour disponible (Update available) card.
- Choose:
- Mettre à jour cette nuit… (Update tonight…), then Programmer pour cette nuit (Schedule for tonight): the update is applied in the night window (4 a.m. to 7 a.m. by default, venue time). This is the normal choice.
- Appliquer maintenant… (Apply now…), then Appliquer maintenant (Apply now): for an emergency. The version is first prepared (download, verification) without interrupting anything; the interruption comes afterwards.
- Follow the update card: Quand (When), Demandée par (Requested by), then, during installation, the current Étape (Step) and the Reprise prévue (Expected resumption).
Each request is recorded in the log, with your name and the time. A scheduled update can be cancelled with Annuler la mise à jour… (Cancel the update…) until it switches to maintenance.
When it cannot start
Section titled “When it cannot start”An update never starts during a transfer in progress on a machine, nor if an open register or tablet has had a money movement in the last 30 minutes (adjustable). Registers that are open but inactive do not block anything: they resume afterwards.
- Tonight: the update is postponed (badge Reportée (Postponed), with the Raison du report (Reason for postponement)) and retried; if the window ends, it moves to the next night, never in the middle of the day.
- Now: it is refused immediately, with the list Ce qui empêche la mise à jour maintenant (What prevents the update now) (for example the transfer in progress on a given machine, or a given person’s register being active). Programmer plutôt pour cette nuit… (Schedule for tonight instead…) carries the request over to the night.
During the interruption
Section titled “During the interruption”The server goes into maintenance for a few minutes (the announced duration, about 3 min by default, then the measured duration of the last update). During this time:
- the registers show “Mise à jour du serveur en cours — les caisses reprennent seules” (Server update in progress — the registers will resume on their own) and grey out money actions; they do not replay anything on their own;
- the back office shows Serveur en maintenance (Server in maintenance) and reloads by itself when the server is back;
- the devices keep their proofs and send them again when the server is back: a transfer completed during the interruption is counted.
Nothing is written during maintenance: no data can be lost.
The steps shown are, in order: checking the conditions, downloading the version, checking the publisher’s signature, unpacking, pre-build checks, preparing the images, switching to maintenance, backing up the database, starting the new version, health checks, reopening.
The automatic rollback
Section titled “The automatic rollback”After installation, the new version must pass its health checks within a given time (5 min by default). Otherwise, the previous version is put back automatically, and the database restored if it had been modified. The latest result card says so:
Retour arrière le 28/09 à 04:09:12 : contrôles de santé en échec — version 2.0.19 remise, aucune donnée perdue.
(Rolled back on 28/09 at 04:09:12: health checks failed — version 2.0.19 put back, no data lost.)
An alert reports it too. You can request the update again later; if it happens again, tell the publisher.
The log
Section titled “The log”Further down, Journal du service de mise à jour (Update service log) (grouped by update: who, when, each step and its duration) and Historique (History) (the requests, cancellations and results from the audit log).
Venue installed another way
Section titled “Venue installed another way”A venue without the update service (badge Pas de mise à jour par bouton (No button updates)) or never linked to a platform receives no version announcement: the screen says so and points to the technician’s installation command (Install a venue PC). A venue already in service is not reinstalled over the top: ask the publisher how to proceed for this PC.