Updating

git pull                       # or download the new version
docker compose up -d --build

Database migrations run automatically on start. Take a backup before a bigger update.

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:

docker compose up -d --build

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

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:

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.

Version stamping and the update check

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

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

Without it the instance reports dev and the update check 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. Set KB_UPDATE_CHECK=0 to turn it off entirely.