Quick start

The simplest route: a guided installation, with prompts walking you through it. Written for whoever is running the installer for the first time. If you are automating instead (scripts, CI), go to Non-interactive use and CI.

Before you start

• Ubuntu ≥ 22.04, Debian ≥ 11 or Fedora ≥ 40;
• a normal user with sudo (do not log in directly as root);
• ≥ 5 GB free; port 8069 free (80/443 too if you will use Nginx).

Nothing else: the installer is a static binary — neither Python nor Rust is needed on the machine.

1. Get the command

The shortest way on Ubuntu or Debian — replace 3.0.0 with the latest version on Releases:

curl -fsSL -O https://github.com/Omisen/invok/releases/download/v3.0.0/invok_3.0.0-1_amd64.deb
sudo apt install ./invok_3.0.0-1_amd64.deb

On Fedora it is the same binary in the other wrapper (invok-3.0.0-1.x86_64.rpm, with sudo dnf install ./...). If you would rather install nothing, download the musl .tar.gz and run it where you unpacked it; if you already have Rust, cargo install invok.

All the routes with their full commands, checksums and trade-offs are in the README. From here on this guide assumes invok is on your PATH.

2. (recommended) See what it will do first

invok --dry-run

--dry-run prints the plan without touching anything. It works without sudo too, but then some steps cannot inspect the system and the plan comes out thinner — the installer tells you so. It is the safe way to find out what will happen. See Verification and troubleshooting.

3. Start the guided installation

sudo invok

The installer asks you, one at a time (press Enter to accept the suggested value):

• Odoo version — pick one of 16.0 / 17.0 / 18.0 / 19.0;
• system user, database name, HTTP port, install directory;
• admin password (masked — do not use admin outside a demo);
• Nginx? — yes/no for the reverse proxy;
• finally a summary and the "Proceed?" confirmation.

While it works you get a progress bar with the current step (the clone and pip install are the long ones). If something fails, the installer undoes its own work and says so — you are never left with a half-installed system. Why you can rely on that: The rollback model.

4. Check that Odoo came up

systemctl status odoo18            # 18 = short version
source ~/.bashrc && odoo status    # helper command

Open http://<server-ip>:8069. Details and common problems in Verification and troubleshooting.

---

Tip: for your first time, try it on a throwaway VM or container. Thanks to the rollback nothing is left behind if it goes wrong, but while learning it is handy to be able to start from scratch.