Windows
Two downloads on the releases page, both 64-bit:
Reaper-<version>-windows-x64-setup.exeinstalls for your account alone, with a Start menu entry and no admin prompt.Reaper-<version>-windows-x64.zipunpacks anywhere and runs from there.
Which build
| Download | Follows |
|---|---|
| the newest release | the stable channel. Use this. |
dev-build | the dev branch, refreshed nightly, for testing what is coming. |
To run the dev channel, download the same two files from the dev-build prerelease on the
releases page and install them the same way. Dev builds change often. Releases are the
steadier channel.
First launch
Start Reaper and your browser opens on http://127.0.0.1:8420 once the server is ready. A
tray icon is the app while it runs: right-click it for Open Reaper and Quit Reaper.
Closing the browser tab leaves the server running; Quit is what stops it.
Where the data lives
%LOCALAPPDATA%\Reaper holds the database, the encryption keys, and launcher.conf. Back up
reaper.db, secret.key, and secret.salt, covered in Back this up.
Updates and reinstalls leave the folder alone.
Settings
A double-clicked app receives no environment variables, so Reaper reads launcher.conf from
the data folder instead. The first run writes it as a commented template: the port, the
listening address, the browser launch, the update check, and the tray icon each have a line.
The tray icon also has a switch in the app, under Settings, General, Desktop app.
Reaching it from other machines
Reaper listens on every interface, the same as the container. Open http://<host-ip>:8420
from the other machine; 127.0.0.1 is only what your own browser opens.
Starting at login
Reaper runs while open and stops when you quit it. To start it with Windows, press Win+R, run
shell:startup, and drop a shortcut to Reaper in the folder that opens.
Updating
Run the new installer over the old install, or replace the unpacked folder. The data folder is untouched either way. Settings, About says when a newer build exists.
Next
First run, in order. The first account to sign in claims the install, so it matters who does it.