Reelora docs
 v1.1.0
Live demo Get help
● Ship · New versions

Updating.
Keep your data, replace the code.

Updates replace the code and keep your data folder and .env. The database schema is created and extended automatically on start, without manual steps.

Keep server/dataKeep .envAutomatic migrations

01Before you update

  • Back up server/data/ and server/.env (how).
  • Read the changelog.
  • If you changed the code, keep your changes in version control (for example git) so you can merge them into the new version.

02Update the server and web player

Windows

Commands on this page are for macOS or Linux. On Windows, run them in WSL (Windows Subsystem for Linux) or Git Bash; PowerShell needs different syntax for some lines.

  1. Stop the server.
  2. Replace the code with the new version. Keep server/data/ and server/.env.
  3. Rebuild both parts.
cd web && npm ci && npm run build
cd ../server && npm ci && npm run build
  1. Start again. The schema is extended automatically on start.

With Docker: build the new image, stop and remove the old container, and run the new one with the same volume (-v reelora-data:/app/server/data).

03Update the apps

Merge your app changes (bundle id, icons, AdMob ids, signing) into the new app/ folder, raise the version in app/pubspec.yaml, build and submit to the stores. Update the server first, then the apps, and check the changelog for changes to the API (docs/API.md).

04Database migrations

Migrations are automatic. On every start the server creates missing tables and columns in reelora.sqlite and admin.sqlite. New console settings appear with their documented defaults (defaults); money switches added in a future version also start off.