Quickstart — self-host

One command to bootstrap Feedbot on a Linux VPS or macOS laptop, with TLS-ready Caddy, Postgres, and the Settings UI.

The shortest path to a self-hosted Feedbot:

curl -fsSL https://get.feedbot.dev | sh

That one line:

Runs pre-flight checks (OS, Docker, ports, time sync).
Auto-detects the install mode (private if you’re on a laptop, public if you’re on a VPS with an internet-routable IP).
Pulls the images from GHCR (api, web, bot, caddy, postgres).
Writes docker-compose.yml, .env, and a Caddyfile.
Starts the stack and waits for healthchecks.
Installs the feedbot CLI to /usr/local/bin/.
Verifies the dashboard is reachable.

Total time: about 30 seconds on a fast network.

Run it without piping

If you want to read the script before running it (recommended for production deploys):

curl -fsSL https://get.feedbot.dev > install.sh
less install.sh        # review
sh install.sh          # run

The installer accepts a handful of flags. Full list with sh install.sh --help.

curl -fsSL https://get.feedbot.dev | sh -s -- --local

Forces local mode: binds to 127.0.0.1, accessible only from this machine. Useful for laptops and dev boxes.

curl -fsSL https://get.feedbot.dev | sh -s -- --server --yes

Forces server mode: binds to 0.0.0.0, accepts traffic from anywhere. --yes skips all prompts (accept defaults).

curl -fsSL https://get.feedbot.dev | sh -s -- --version=v0.2.0

Locks the install to a specific image tag. Great for reproducible deploys.

curl -fsSL https://get.feedbot.dev | sh -s -- --dry-run --local --workdir=/tmp/feedbot

Generates the workdir + config files but doesn’t touch Docker. Inspect the result, then re-run for real.

After install:

A running stack at http://<your-IP> (server mode) or http://localhost (local mode).
A feedbot CLI on your PATH.
A /opt/feedbot/ (or ~/.feedbot/) directory with everything Feedbot needs.
The dashboard’s Settings page — that’s where you set up SMTP, Telegram, your domain, and HTTPS. No .env editing required.