Vault Setup Guide

One shared game library, set up right.

The full technical walkthrough: pairing the Vault Server, installing the Node app on every PC, designating an Update PC, and (the step most guides skip) actually publishing what it installs.

Chapter 7 · The most-missed step

Install games and publish them

Install or patch a game on your Update PC exactly like you would on any normal PC: Steam, Epic, whatever launcher.

Heads up

That install stays local to the Update PC until you explicitly publish it. Nothing else on the floor sees it yet. This is the step almost every new Vault setup misses.

On the Center panel's Vault page, find the Update PC's row in the Machines table and click Publish. That's it, no need to touch either PC directly.

Publishing takes a moment. When it finishes, the Update PC gets a clean fresh mount, and every other PC on the floor picks up the change on its own. No restart needed on their end.

Note

Do this every time after installing something new or patching an existing game. It never happens automatically.

If your café's internet is down

The Publish button needs the Server to reach the cloud. If it's offline, you can still trigger the same publish locally:

Option A: no command line

On the Update PC itself, create an empty file named seal-requested inside %ProgramData%\LANBear\Vault\. The Node role picks it up on its next check and starts publishing.

Option B: command line, run on the Server PC

From an elevated prompt in the LANBear Vault install folder, LANBear.Vault.exe cli server node-seal --id <node-guid>, using the Update PC's node ID as shown on the Center panel's Machines table.