Install a venue PC

A new venue goes live in three steps: the owner creates the venue online and receives a link code, the technician types one single command on the venue PC, then the owner confirms that it really is their venue. This is the only time the technician uses a terminal; everything else is done in the back office.

1. The owner creates the venue and sends you the code

📍 Where in the online back officeCompagnie (Company)→Salles (Venues)→Ajouter une salle (Add a venue)Who can:OwnerCompany administrator

The owner enters the venue’s name, time zone and currency. The screen then shows, only once:

• the link code (8 characters, for example XXXX-XXXX), usable only once and until the expiry shown;
• under the heading PC neuf : la commande du technicien (New PC: the technician’s command), the full command, ready to copy, with the Copier la commande (Copy the command) and share buttons.

The owner sends it to you (text message, WhatsApp). If the code is lost or sent to the wrong person, the owner clicks Nouveau code (retire celui-ci) (New code (withdraws this one)): the old code stops working.

“Aucune version de la salle n'est encore publiée par l'éditeur” (No venue version has been published by the publisher yet)

If the screen shows this sentence instead of the command, one-command installation is not possible yet on this platform: tell the publisher. The command is never shown when it cannot work.

2. You type the command on the venue PC

Prepare the PC (see The venue PC): Ubuntu 22.04 or 24.04, connected to the venue network, with Internet. Open a terminal and paste the command you received. It looks like this:

📍 Type on: Venue PC (Ubuntu)

wget -nv -O- https://<adresse de votre plateforme>/installer | sudo bash -s -- --code <CODE>

If the PC does not have wget, the same thing with curl:

📍 Type on: Venue PC (Ubuntu)

curl -fsSL https://<adresse de votre plateforme>/installer | sudo bash -s -- --code <CODE>

The password requested is the one for your Ubuntu account (for sudo). The command then runs through its steps on its own and shows them:

1. PC checks, before touching anything: the system (Ubuntu 22.04 or 24.04), the processor (64-bit), at least 10 GB free, Internet access to the platform, the PC’s clock, and that no other program is using what the venue needs. A problem is shown in red (🔴) with the command that fixes it, and nothing is installed.
2. The server version: the current version is downloaded from the platform. The PC only installs a version signed by the publisher: a modified archive is refused.
3. System packages and, if needed, Docker.
4. Installation and start-up. The first start can take several minutes (new database).
5. Linking to the platform with your code.

At the end, the command shows “✔ Serveur de salle Lucky Touch … installé” (Lucky Touch venue server … installed), the venue back office address, the initial administrator’s username and the command that shows their password. This password is never shown on screen during installation: it is stored on the PC, readable only by the PC’s administrator. Change it at your first sign-in to the back office.

An interruption? Run the same command again

An interrupted installation (power, network, a program to stop) resumes when you run exactly the same command again: nothing is done twice, and neither the database nor the settings are recreated. The code is only used up at linking: if it has expired in the meantime, ask the owner for a new code and run the command again with this new code.

If linking fails

The venue is then installed and running; only the link is missing. The command says so and offers two ways forward:

• a new code requested from the owner, then the same command run again with this code;
• or, without a terminal: in the venue back office, Paramètres (Settings) → Plateforme (Platform), enter the code in Code de rattachement (Link code), then Rattacher (Link) (see Linking the venue). Then run the command again to finish the installation.

If Lucky Touch is already installed on this PC

The command refuses to reinstall over a running venue, and says what to do: updates go through the back office button (Updating a venue); a reinstallation is done on a new PC, with the backup (Restore onto a new PC).

3. The owner confirms “C’est bien ma salle” (This is my venue)

📍 Where in the online back officeCompagnie (Company)→Salles (Venues)Who can:OwnerCompany administrator

As soon as it is linked, the venue appears at the top of the list with “Une salle vient de se rattacher : est-ce bien la vôtre ?” (A venue has just linked: is it yours?) and what it declared: Nom du PC déclaré (Declared PC name), Première connexion (First connection), Depuis l’adresse (From address), Devise (Currency), Version. The owner checks this information with you (the PC name, the installation time), then clicks C’est bien ma salle (This is my venue).

Until this is done, the venue already sends its data but receives nothing from the company (no people, no PINs). If it is not theirs, Ce n’est pas ma salle… (This is not my venue…) cuts off this server and gives a new code.

Check the script before running it (optional)

The command downloads a public script, served by your platform, which contains no secret. If you want to make sure it has not been modified, ask the publisher for its fingerprint, then compute it on the PC with wget -qO- https://<adresse de votre plateforme>/installer | sha256sum and compare the two.

Next steps

• The venue PC: what you need to know so that it runs for a long time.
• Back up and restore: set the recovery phrase and adopt a USB stick, the same day.
• Install a register and Devices and firmware.