Skip to content

Updating ​

bash
./backup.sh                    # 1) backup — see below why always
git pull                       # 2) new code (or a new ZIP — see below)
docker compose up -d --build   # 3) rebuild and start

Database migrations run automatically on start. An update never overwrites your .env, docker-compose.override.yml or pb_data.

Before updating: a backup ​

Migrations run forward only. If you want to go back to an older version, the only way is to restore a backup from before the update — PocketBase cannot roll migrations back (the server runs with --automigrate=0). ./backup.sh before git pull takes a few seconds; see Backup and restore.

Always --build ​

The application and all its server-side logic are baked into the image. After any change — new code, or an .env variable such as TZ — you need:

bash
docker compose up -d --build

docker compose restart keeps running the old build without telling you.

Updating from a ZIP (without Git) ​

If you downloaded the code as a ZIP (the Windows route in Installation):

  1. Download the new ZIP from the releases page and unpack it next to the old folder.
  2. Copy only three things from the old folder into the new one: pb_data (the data), .env (the configuration) and docker-compose.override.yml if you have one.
  3. In the new folder run docker compose up -d --build. Delete the old folder once the new one has proven itself.

Everything else (docker-compose.yml, backup.sh, the code) belongs to the version and is replaced.

After updating, check ​

bash
docker compose ps                       # the service is "Up"
docker compose logs killbottleneck      # ends with a "Server started" line

Migrations run quietly — only the ones that recompute something (project numbering, say) show in the log. A failed migration, on the other hand, stops the start: the service restarts in a loop and the error is in the log. In that case restore the backup and tell us (Discord or bug reports) — do not run the old image over the new data.

In the app, menu by your name → About then shows the new version. The same place tells you about the next one: the Version … is available line links to the release notes.

About — here you see what is running and whether a newer release exists.

Version stamping and the check for new versions ​

Pass the version at build time so the instance knows what it is running:

bash
KB_VERSION=$(git describe --tags --dirty) docker compose up -d --build

Without it the instance reports dev and the check for new versions is not offered — which is what you want for work in progress.

The check itself runs in the signed-in user's browser, which asks the GitHub API whether a newer release exists. The instance sends nothing anywhere; there is no telemetry.

Pre-releases (-rc) are opt-in — KB_UPDATE_PRERELEASE=1

By default the check offers stable releases only (v1.0.0 and later). If you also want to hear about release candidates (v1.x.0-rc1), set KB_UPDATE_PRERELEASE=1. KB_UPDATE_CHECK=0 turns the check off (and KB_HOSTED=1 does so automatically); a fork of your own reads from KB_UPDATE_REPO. If you are still on a v0.xx-beta, the check offers v1.0.0 as usual.

What changes between versions ​

Every release has an Upgrade notes paragraph in the CHANGELOG. Usually it says "no configuration changes". When it is worth reading before you run --build:

ReleaseWhat awaits you after the update
v0.87New variables KB_NAVRAT_* (come-back e-mails, need SMTP; KB_NAVRAT_MAILY=0 turns them off). E-mail subjects start with the organization name.
v0.86Migrations of client and invoicing fields (invoices from the assistant) — no action.
v0.84Nodes carry an optional icon field in the REST API and MCP.
v0.83The migration adds shared calendars; going back to an older version deletes them. A new instance gets the Company and Time off calendars (KB_UVODNI_MAPA=0 switches that off).
v0.79Every existing user sees the Connect your AI agent dialog once. KB_AGENT_SETUP_ASK=0 switches it off — but the shipped docker-compose.yml does not pass that variable through yet, so it belongs in docker-compose.override.yml (see the reference).
v0.68The default KB_CHAT_TOOLS is auto (was groups); the Suggest with AI and Map from text dialogs were replaced by the assistant.
v0.65Anyone with their own compose/override adds KB_PURPOSE_ASK, KB_AI_OPENAI_EXTRA, KB_CHAT_TOOLS, KB_VISION_ZALOHA_NUM_CTX.
v0.63Migrations for events and reminders — rolling back deletes them.
v0.61The assistant collections (ai_chats, ai_memory, ai_chat_log), the KB_VISION_* and KB_SHARE_INVITE_* variables.

The rule that follows from the table: a migration that adds something deletes it, data included, when you roll back — hence the backup before updating.

Rolling back ​

  1. docker compose stop
  2. git checkout v0.86-beta (or unpack the older ZIP)
  3. ./backup.sh restore kb-backup-….tgz from the backup taken before the update
  4. docker compose up -d --build

Without a backup from before the update, the older version will not come up correctly over the new data.

One-off: upgrading from v0.11 or earlier ​

After the product was renamed, the container is called killbottleneck instead of flowmap. The old container still holds port 8090, so the new one cannot start. Remove it first:

bash
docker rm -f flowmap
docker compose up -d --build

Your data is in the ./pb_data folder on disk, not in the container — you lose nothing. FLOWMAP_* variables in your .env keep working; there is no need to rewrite them.

Open source under the MIT license · © Tengo s.r.o.