lemonfiber is one binary with one subcommand at a time. Run it with no
subcommand at all on a machine that is already set up and you get
the terminal interface instead.
Every subcommand below accepts the same four global flags,
and every one of them has a machine-readable form. The tables here say what each
command is for; the full generated reference, with every argument and flag,
is the complete command reference — generated from the
binary at the revision this site pins, which that page names at its foot.
Global flagsThe four flags every subcommand takes, and the ones that only look global.
Lists everything that leaves this machine, and what refusing each of it costs
You want to know what lemonfiber asks the internet for, what the services ask for on their own account, and what switching each off would stop
stored
Lists what lemonfiber keeps on this machine, where it is, and why
You want to know what is on your disk because of lemonfiber, and to be sure your library is not part of it
credentials
Says which credentials this stack holds, or acts on one of them
You want to know what secrets exist, what each is for and where it stands. Values are never printed by a read
forget
Removes everything lemonfiber keeps on this machine
You are done with it. Your library, your downloads and the containers are never touched; it lists what would go and does nothing until --confirm
uninstall
Takes lemonfiber off this machine, at one of four removals
You are removing it and want to choose how far that goes. It lists what each removal would take before it takes anything
outbound says what would leave. What actually left is written down as it goes,
in outbound.log beside your settings: when, which kind of request, where it
went, and what came back. Never a header, never a body, and the address arrives
with its query stripped off, because a search term, a title or an indexer key
ends up there — a record kept to reassure you should not be a file full of your
own keys. It holds the last five hundred lines, oldest dropped, and stored
lists it with everything else.
Serves the JSON API on a loopback socket for as long as you leave it running, printing the address and a token minted for that run
You are driving lemonfiber from a browser, a client or a script rather than a terminal. --assets <dir> serves a built web app beside it; --lan offers it to your network, once --set-password has set one
The global flags apply to all of the above, and
the terminal interface is what you get when you run none of
them. If you are following what a command told you rather than choosing one,
when something is wrong starts with the doctor. If you are writing a
script against the output rather than reading it,
the API and the SDKs describe the shape it arrives in.