Install launchroom

launchroom installs with one command on any Linux server that runs Docker. After a few minutes:

• the dashboard runs on its own HTTPS address,
• the server can build and run your apps,
• you create the owner account in the browser.

Every install follows two rules:

• It's Docker containers and a folder. Everything launchroom needs lives in one folder, ./launchroom by default.
• Nothing is written outside the folder. The installer installs no packages, writes nothing to /etc, creates no systemd units and never edits Docker's daemon.json. Outside the folder, launchroom only creates Docker objects (containers, images, volumes, networks) labelled launchroom.managed=true.

RequirementsCopy Anchor Link

If Docker is missing, the installer prints the link to Docker's official install instructions and stops. It never installs Docker for you. If the server has less than 2 GB of RAM, it warns and continues.

Run the installerCopy Anchor Link

curl -fsSL https://launchroom.vantezzen.io/install | sh

The folder is created where you run the command. Run it in the directory you want launchroom/ to live in, for example your home directory.

Your own domain or the automatic addressCopy Anchor Link

Without options, the dashboard gets an automatic address built from the server's public IP: https://203-0-113-10.sslip.io for a server at 203.0.113.10. It has a real certificate and needs no DNS.

If you already have a name for the dashboard, pass it with --domain and point an A (or AAAA) record at the server first:

curl -fsSL https://launchroom.vantezzen.io/install | sh -s -- --domain dash.example.com

Use a stable name if you have one. If the server has to be rebuilt from a backup, you only change DNS and every other server reconnects by itself. You can also move the dashboard to a domain later, from the dashboard, without reinstalling. See Dashboard domain.

What the installer doesCopy Anchor Link

Create the owner accountCopy Anchor Link

Open the setup link the installer printed (https://<your dashboard>/setup?token=…). The first-run screen confirms the install and asks for your name, email and a password. This account becomes the instance owner.

If the setup link expired, run ./launchroom setup-token in the install folder for a new one.

After sign-in, Get started guides you through the remaining steps:

1. Connect GitHub.
2. Set an address for your apps.
3. Deploy the first app.
4. Set up backups.

Get started also recommends two-factor authentication. It is optional.

The install folderCopy Anchor Link

launchroom/
├── compose.yml              managed: replaced on upgrade (do not edit)
├── compose.override.yml     yours: optional overrides (ports, resource limits)
├── .env                     generated secrets, settings and image pins (0600)
├── launchroom               helper script
├── guard/                   the pinned release identity for updates
└── data/
    ├── keys/                encryption and signing keys
    ├── postgres/  valkey/   control-plane state
    ├── zot/                 the image registry's config and storage
    ├── headscale/           the private network's coordination state
    ├── daemon/              launchroomd's identity, last desired state, cached proxy config
    └── backups/             control-plane backups to a local destination

Put local changes to the stack in compose.override.yml. compose.yml is replaced on every upgrade.

The ./launchroom helperCopy Anchor Link

Run these from inside the install folder.

Installer optionsCopy Anchor Link

Pass options after sh -s --, for example curl -fsSL https://launchroom.vantezzen.io/install | sh -s -- --dir /srv/launchroom.

Upgrading is re-running the installerCopy Anchor Link

Running the same command again is safe. It is how you move to a new release:

• .env and everything in data/ are kept.
• compose.yml, the helper script and the image pins are replaced.
• The stack is brought up to date, and this server's launchroomd stays connected.

Run it from the same directory, or pass --dir to point at the existing folder.

You can also update from the dashboard. Settings → Updates takes a backup, updates the control plane and then every server, and rolls back if the new version doesn't come up. See Updates.

UninstallCopy Anchor Link

./launchroom uninstall

The command asks twice:

1. Type uninstall to stop the stack, remove launchroomd's firewall rules and remove every container and network labelled launchroom.managed=true, including your deployed apps, Caddy and BuildKit.
2. Type delete to also remove the labelled volumes (your databases and app data), the images those containers used and the folder. Skip this step and your data stays on disk.

Other servers you added have their own small install folder. See Uninstalling a server.

Next stepsCopy Anchor Link