Windows
You'll find two 64-bit downloads on the releases page:
Reaper-<version>-windows-x64-setup.exeinstalls to your account without an admin prompt and adds a Start menu entry.Reaper-<version>-windows-x64.ziplets you unpack the files anywhere and run them from that location.
Which build
| Download | Follows |
|---|---|
| the newest release | the stable channel. Use this. |
dev-build | the dev branch, refreshed nightly, for testing what is coming. |
Download the same two files from the dev-build prerelease on the releases page to run the dev channel and install them the same way. Dev builds change often. Releases are the stable channel.
First launch
Start Reaper and your browser will open to http://127.0.0.1:8420 once the server's ready. While it's running, you'll see a tray icon. Right-click it to select Open Reaper or Quit Reaper. Closing the browser tab keeps the server running, so use Quit to stop it.
Where the data lives
Your database, encryption keys, and launcher.conf are stored in %LOCALAPPDATA%\Reaper. Back up reaper.db, secret.key, and secret.salt as described in Back this up. Updates and reinstalls won't touch this folder.
Settings
Reaper reads launcher.conf from your data folder. On the first run, it writes a commented template with lines for the port, the listening address, the browser launch, the update check, the tray icon, and recovery mode. You can find a switch for the tray icon in the app under Settings, General, Desktop app. If you can't sign in, use recovery mode as explained in Not getting locked out.
Reaching it from other machines
Reaper listens on every interface, just like the container. Open http://<host-ip>:8420 from your other machine. Use 127.0.0.1 only if you're using a browser on the same machine.
Starting at login
Reaper runs while it's 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. Your data folder stays untouched either way. Settings, About says when a newer build exists.
Next
Follow the First run steps in order. The first account that signs in claims the install, so make sure you know who's doing it.