How a release reaches a venue

This page explains, for everyone, the path a new Lucky Touch version takes to reach a venue. The publisher’s own steps are in its private documentation; the venue’s steps are in Updating a venue.

The path, in five stages

The publisher builds the version: an archive containing the venue server, its back office and, when it is ready, the register application for each device type. The publisher signs it: only an archive signed by the publisher will be accepted by a venue.
The platform is updated first. A venue version is never more recent than the platform that announces it: the platform refuses to publish a version more recent than itself.
The publisher publishes the version on the platform. It becomes the version announced to linked venues, and the one installed by the installation command on a new PC.
The venue applies the version: the administrator sees “Mise à jour disponible” (Update available) in the back office and chooses tonight or now. The server checks the signature, backs itself up, installs, checks itself, and goes back on its own to the previous version if the checks fail.
The registers follow: the venue server serves its registers the application that goes with its version. Each register offers it when it is not in service, and updates with one tap.

What this path guarantees

Only the publisher can produce a version. A compromised platform cannot push a version: it cannot sign it, and the venue refuses any archive not signed by the publisher.
The venue decides when. Nothing is installed without an action by the venue’s administrator (in the venue back office or the online back office). And 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 by the venue): it is then postponed, with the reason shown. An open but idle register does not prevent anything (see Updating a venue).
No loss. The server backs itself up before installing, writes nothing during the interruption and puts back the previous version if the new one fails its checks.
No Internet for the registers. Tablets and register PCs download their update from the venue server, on the local network, in a few seconds. The register offered is exactly the one that goes with the server.
A new PC starts from the right version. The installation command for a venue PC downloads the current published version; it is in fact only offered to the owner once a version is published and usable.

Special cases

A version withdrawn by the publisher is not published again: a fix always comes under a new number.
An offline venue receives the announcement at its next contact; an update request sent from the online back office is applied by the venue itself.
A version without a register: a published version sometimes does not yet contain the register application. The Postes de caisse (Register devices) screen says so (“Aucune caisse servie” — No register served). Registers already installed stay on their version: nothing is offered to them. A new register device is installed separately, with the installer supplied by the publisher.