kevinveenbirkenbachandClaude Opus 5 a0a24e2c0e feat(i18n): deploy libretranslate into the i18n runner before translating ...

server() now resolves a translation endpoint in three steps: use the running
service, rebuild when the host has a GPU but no accelerated deploy left its
stamp, otherwise deploy. A plain run therefore costs nothing, and the rebuild
fires once, on the move from a CPU-built container to an accelerated one.

deploy() brings the runner up, waits for State.Running and deploys the role
inside it. The exec steps address `docker compose exec i18n` directly:
cli.administration.deploy.development exec hardcodes the `infinito` service
(compose.py:261), so every deploy through it silently ran in the main
container, where mailu already holds port 25 and postfix cannot start.
check=True stops a failing step instead of carrying on against the wrong
target.

The deploy router writes its pid to build/deploy.pid, which survives the exec
into the subscripts, and deploying() refuses a translation while that process
lives. The running deploy is left untouched.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-09-24 01:53:19 +02:00

..

administration

feat(i18n): deploy libretranslate in an isolated compose runner

2026-09-24 01:37:37 +02:00

build

feat(i18n): deploy libretranslate into the i18n runner before translating

2026-09-24 01:53:19 +02:00

console

…

contributing

…

core

…

deploy

…

fix

…

gha

…

meta

fix(ci): narrow a row's architectures by what its variant deploys

2026-09-22 16:01:09 +02:00

setup

…

__init__.py

…

test_entrypoint_main.py

…

test_inventory_manager.py

…