Updating Rostyman

Your data is local and stays yours. Updates carry everything over automatically — this is just the safe way to do it: back up in a minute, update, and restore if you ever need to.

Back up first — it only takes a minute.While installing the new version, the updater can clear Rostyman's data folder. Everything you've created lives in a single file, so copy it aside first and put it back afterward — then you keep all your collections, history, environments, and settings, guaranteed.

1

Back up your data

Everything you've created lives in a single file, rostyman.db. To back it up:

  1. Fully quit Rostyman — so the database is flushed and the copy is complete.
  2. Copy rostyman.db from the folder for your system to somewhere safe (Desktop, cloud drive, USB):
Windows%APPDATA%\Rostyman\rostyman.db
macOS~/Library/Application Support/Rostyman/rostyman.db
Linux~/.config/Rostyman/rostyman.db

Moved your data elsewhere via Settings? The real location is in data-location.json in that same folder (the dbPath field).

Prefer a lighter backup? In the app, File → Export saves your collections to a file you can re-import.

2

Update to the latest version

Grab the newest build from the releases page and install it:

Get the latest Rostyman

  • Windows: run the installer over your current version. It may clear the data folder during the swap — that's exactly what your Step 1 backup + Step 3 restore cover.
  • macOS: open the .dmg and drag Rostyman into Applications, replacing the old one. Your data stays in place.
  • Linux: replace the AppImage or install the new package. Your data stays in place.

Once your database is in place, the app upgrades it automatically on launch — those changes are additive and safe.

3

Restore your backup

On Windows, do this after updating to bring your data back (macOS & Linux: only if something looks missing). Because your data is one file, it's simple:

  1. Fully quit Rostyman.
  2. Replace rostyman.db in the folder above with your backup copy.
  3. Relaunch — you're exactly where you left off.

Something not right after updating? Get help — we respond on GitHub Issues, or email [email protected].