Install Eddyline
Run one line on a fresh server and your team is working in 15 minutes. The installer sets up Docker, the database and HTTPS for you. Read what it does.
curl -fsSL https://get.eddyline.app | sh To read the installer before you run it, see how to check it.
Requirements
- Ubuntu 22.04 or 24.04, or Debian 12
- amd64 or arm64
- 1 GB of RAM, 2 GB recommended
- Ports 80 and 443 free
- A DNS A record pointing at the server
Flags
The installer asks for what it needs. For scripts, pass these flags instead.
| Flag | What it does |
|---|---|
--domain | The address your team will use. Required. |
--email | Contact address for Let's Encrypt. |
--license | A licence key, from a trial or a purchase. |
--smtp-url | Your SMTP server, so Eddyline can send mail. |
--mail-from | The sender address for outgoing mail. |
--version | The version to install. The default is stable, which is resolved to a number and pinned. |
--yes | Skip the prompts, for scripts. |
--no-tls | Plain HTTP on port 80, for CI and testing on a LAN. |
--database-url | Advanced: use an existing Postgres instead of the bundled one. |
Advanced: external database
If you already run Postgres, pass --database-url and Eddyline uses it instead of the bundled one.
Read the full steps.
- Postgres 14 or newer.
- An empty database owned by the app's role, with the citext extension available. The role can create citext without superuser.
- Reachable from Docker. For Postgres on the same host, use host.docker.internal as the host.
- Percent-encode special characters in the password, such as @, / and :.
- The installer checks the connection and the database before it writes anything. It never migrates a database that belongs to another app.
What happens next
- Open the setup link. The installer prints a setup link when it finishes. Open it in your browser.
- Create the workspace. Name the workspace and create the first admin account.
- Add a licence key. Optional: paste the key from your trial or purchase. Without one, Eddyline runs as the Free edition.
- Finish the setup. Point DNS at the server if you have not yet, set up email, and register the callback URL for Google or OpenID Connect sign-in if you use it.