Eddyline docs
Install Eddyline on your own server, set it up, and run it. Then learn the parts your team uses every day. Start with the install guide, or the install page if you want the one-line command.
Self-hosting
- Install Draft
Install Eddyline on your own server with one command, what the installer checks, the flags it takes and what happens next.
- First-run setup Draft
Use the setup link to name your workspace, create the first staff account and set your staff email domains.
- Licence and team members Draft
How editions and team members work, why clients never count, what happens at the limit or when updates end, and how to enter or renew a key.
- Email Draft
Set up outgoing mail with SMTP or SendGrid, what happens with no mail set up, and how to copy invite links by hand.
- Sign-in methods Draft
Password, Google and OpenID Connect sign-in, the callback URLs to register, and the rules for trusting an email address.
- Backups and restore Draft
The nightly backup, how to copy it off the server with a hook, and how to restore it.
- Updates and the update check Draft
Update with one command, what the daily update check sends, and how to turn it off.
- External database Draft
Use your own Postgres, or a managed one with point-in-time recovery, instead of the bundled database.
- What leaves the server Draft
Every outbound connection an Eddyline install makes, when it happens, and whether you can turn it off.
- The eddy command Draft
Every subcommand of the eddy management command: status, logs, update, backup, restore, config, restart, create-admin, set-license and uninstall.
- Troubleshooting Draft
Check status, read the logs and test the health endpoint when an install does not come up or stops answering.
Using Eddyline
- Issues Draft
Create and track issues: types, priority, status, assignee, labels, comments, attachments, history and moving an issue between projects.
- Board Draft
The board shows one column per status. Drag cards to change status or order, and filter by search or assignee.
- Project docs Draft
Write specs and notes next to the issues: Markdown pages that are Internal or Shared with clients, with versions and attachments.
- Time tracking Draft
Log time on issues, set estimates, and report hours by person and issue with saved date ranges and CSV export.
- Clients and roles Draft
Invite clients for free, choose what they can see and do per project, and understand the four roles.
- REST API Draft
Read and change issues, docs and time over HTTP with a personal token: authentication, conventions, errors and the rate limit.
- MCP and AI tools Draft
Connect Claude and other AI tools to your install so they can work on issues, docs and time as you, with your access and nothing more.