v1.6.10 — live updates work again

The headline is small to describe and easy to miss: live updates have not worked since 1.6.0, and now they do.

Security

• The service that answers the app's data requests is two major versions newer. It sits between your browser and the database and had been pinned to a build from 2023. Nothing about how Kinboard talks to it changes. Two leftover settings that copied the signing secret into the database session — where any function could have read it — are gone; nothing was using them.
• The live-updates service is around 75 releases newer. It had been pinned to a build from early 2024, still carrying settings from a hosting platform Kinboard never ran on. Nothing changes in the app; it applies its own database updates on first start, so give it a minute longer than usual to come up.

Fixed

• Changes from other devices now appear straight away again. Since 1.6.0 the live connection had been carrying the wrong credentials, so the server correctly decided it was allowed to see nothing and sent nothing. It never looked broken — the connection itself was healthy, so the "live updates paused" warning never appeared — and screens simply refreshed on their own schedule instead, up to a minute behind. Adding something on a phone should once again show up on the kitchen display while you are still standing there.

About the live-updates fix

If a change made on one device only showed up on another after a delay — or on the wall display, sometimes not until something else happened — this is why. The live connection was being opened with the wrong credentials, so the database correctly decided it was allowed to see nothing, and sent nothing.

It never looked broken. The connection itself was healthy, so the "live updates paused" warning never appeared, and screens still refreshed on their own schedule. It read as an app that was occasionally behind rather than one with a missing feature.

The always-on display was affected worst: it never gets focused or switched to, which is what normally triggers a refresh elsewhere.

Upgrading

docker compose -f docker-compose.yml -f docker-compose.image.yml pull
./start.sh up

Both -f flags matter — see v1.6.9 if you missed that one.

The live-updates service applies its own database updates on first start, so give it a minute longer than usual. Nothing to reconfigure and no re-joining.

Take a backup first. Those updates cannot be undone by putting the old version back — see the notes in #126 if you need to roll back.

With this release nothing in the underlying stack is still on a 2023 or 2024 build.