Snap
sudo snap install scythe-labs-reaper
Reaper then serves on http://localhost:8420 and runs as a service: snapd starts it at boot
and keeps it updated. Both amd64 and arm64 are published.
Which channel
| Channel | Follows |
|---|---|
stable | releases. Use this. |
edge | the dev branch, refreshed nightly, for testing what is coming. |
To run the dev channel, switch to edge: sudo snap refresh --edge scythe-labs-reaper. Dev
builds change often. Releases are the steadier channel.
Controlling the service
sudo snap stop scythe-labs-reaper # start and restart work the same way
snap logs scythe-labs-reaper
Where the data lives
/var/snap/scythe-labs-reaper/common holds the database and the encryption keys. Back up
reaper.db, secret.key, and secret.salt, covered in Back this up.
Refreshes leave the folder alone.
Reaching it from other machines
Reaper listens on every interface, the same as the container. Open http://<host-ip>:8420
from the other machine.
Next
First run, in order. The first account to sign in claims the install, so it matters who does it.