Upgrading

Pull the new version and deploy again. Tables are created or updated on the first request.

git pull
npm install
npm run deploy

Upgrading from a version without a database

Early versions kept the admin password in config/admin.json in the bucket and the session index in the bucket too. Both now live in the database.

  1. Add a D1 or Hyperdrive binding as described in the deployment guide. Without it, every request returns 500.
  2. Set SETUP_TOKEN with npx wrangler secret put SETUP_TOKEN.
  3. Deploy, then set the admin password right away. The dashboard asks for setup again because the old password file is no longer read.

config/admin.json, index/* and sessions/*/summary.json in the bucket are no longer used and can be deleted. Recordings made before the upgrade stay in the bucket but do not appear in the session list, because they are not imported into the database.