# Install

> Install on a Linux host with Docker and systemd, mint a CLI token, and update in place.

Source: https://oddk.dev/docs/install/
Project: https://github.com/AndrianBdn/oddk


On a Linux server with Docker and systemd:

```bash
curl -fsSL https://oddk.dev/install | sh
```

Pin a specific version:

```bash
curl -fsSL https://oddk.dev/install | sh -s -- --version v0.1.82
```

The installer downloads the release binary from GitHub, verifies it against the
published `SHA256SUMS`, and then:

- installs the binary to `/usr/local/bin/oddk`
- creates a dedicated `oddk` service user (no login shell) with state under
  `/var/lib/oddk` (`data/`, `backups/`)
- installs and starts the systemd unit `oddk.service`
- configures the CLI for the user who ran the installer, writing
  `~/.config/oddk/cli.json`

That last step means whoever runs the installer can use `oddk` immediately — no
`sudo`, no becoming the `oddk` user.

{{< callout type="info" >}}
**Installing and updating are the same command.** Re-run it any time: on an
existing install it swaps the binary in place, restarts the service, and keeps
the previous binary as `oddk.prev` for instant rollback.
{{< /callout >}}

Before updating, skim the [changelog](https://github.com/AndrianBdn/oddk/blob/main/CHANGELOG.md).
Most releases need nothing from you — the entries marked **Action** do.

