Install
Get Lemonfiber running
Early days: the binary builds from source and the stack runs from Compose. Packaged installs arrive with the first full release.
Build the binary
A stable Rust toolchain is all you need. This builds the same binary the release workflow will publish.
cargo install --git https://github.com/lemonfiber/lemonfiberRun the stack
The stack is a Compose project, and Lemonfiber is the tool that drives it. You can also clone and run it directly — useful if you want to read exactly what is being started before anything starts it for you.
git clone https://github.com/lemonfiber/media-stack
cd media-stack
docker compose up -dDownloads and media must sit under one mount point, or imports copy instead of hardlinking — slower, double the disk, and it breaks seeding. Lemonfiber checks this rather than assuming it.
Not yet: packaged installs
Homebrew, the shell and PowerShell installers, and signed binaries for macOS, Linux and Windows are all produced by the release pipeline, which is milestone M6 and has not shipped. The tap exists but holds a generated placeholder, so `brew install` will not work yet.
When M6 lands, the formula is written by CI rather than by hand and the binaries attach to the GitHub release — at which point they appear in the section below automatically, because this page reads them from the release rather than from a list kept here.
Prebuilt binaries
This release ships no attached binaries yet — build from source, or see the release notes: v0.1.0
Then what
Boot a slice rather than the whole stack. `lemonfiber up tv` starts search, download, organise and subtitles — nothing else. `lemonfiber up full` starts eighteen services. `lemonfiber doctor` tells you whether it is genuinely working, including a hardlink test and a public-IP comparison that proves the VPN is not leaking.
lemonfiber up tv
lemonfiber doctor
lemonfiber down