Answerbell docs
 v1.2.0
Live demo Get help
● Ship · New versions

Updating
to a new version.

Your data and settings live outside the code, in data/ and .env. An update replaces the code, compiles it again and keeps both.

Keep data/ and .envpnpm install && pnpm build

01Steps

Windows

On your server use the Linux shell; on a local copy run the commands in WSL or Git Bash.

  1. Read CHANGELOG.md of the new version (also on Changelog).
  2. Back up data/ and .env (Backups).
  3. Stop the server: sudo systemctl stop answerbell.
  4. Replace the files except data/ and .env.
  5. Install, compile and start:
pnpm install && pnpm build
pnpm test                         # optional, offline
sudo systemctl start answerbell

The database schema is created and extended on start; there is no separate migration step. Forgetting pnpm build leaves the old compiled code in dist/ running.

02After the update

Open Status. If Every client's agent is up to date warns, press Update N agents on the Clients page: it pushes every out-of-date agent at once. Agents made before an upgrade get the new tools then (for example caller_history in 1.2 and the post-call labels in 1.1).