From 8dc2e7d2f11aee4e70c3675e4ba6dd255a47e0e4 Mon Sep 17 00:00:00 2001 From: Anders Betts Date: Wed, 23 Sep 2026 11:51:44 +0200 Subject: web: ship glibc C.utf8 so the web TUI shows åäö MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The cross-built bokftui is static glibc; in the Alpine web image it found no locale data, setlocale() failed and åäö were invalid bytes. The cross build now copies Debian's C.utf8 into the image and the image build runs bokfweb --check-locale, so a TUI without UTF-8 fails the build. Co-Authored-By: Claude Opus 5.5 --- docs/DEPLOY.md | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'docs/DEPLOY.md') diff --git a/docs/DEPLOY.md b/docs/DEPLOY.md index 99b7661..008093f 100644 --- a/docs/DEPLOY.md +++ b/docs/DEPLOY.md @@ -276,6 +276,10 @@ browser ──443──▶ host Caddy (TLS) ──▶ 127.0.0.1:8790 bokf-web c Port 443 is already forwarded for the other sites. The container publishes 8790 on the host's loopback only, so it is unreachable until that block exists. +- **UTF-8**: the cross-built binaries are static glibc, which needs its own + locale data; the image ships Debian's `C.utf8` in `/usr/lib/locale` and + the build runs `bokfweb --check-locale`, so an image whose TUI could not + show åäö fails to build instead of shipping. - `BOKF_WEB_MAX_SESSIONS` (default 20) caps concurrent terminals. `docker compose logs web` shows logins, logouts and failed attempts (never passwords). -- cgit v1.3