Move to soliplex 0.93
Part of Upgrading an existing stack.
Walk this rung with the v0.24 skill release —
its generator produces the rung's end state. The stack being upgraded names
the release that generated it in its own [tool.soliplex-template] manifest —
use that one when climbing from an older shape.
This rung moves the stack to soliplex 0.93, haiku.rag-slim 0.112.0 and
the 0.117 web client. What changes:
- the releases: soliplex from the moving
0.89image tag to0.93, and the ingester fromhaiku.rag-slim0.104.0to0.112.0; soliplex brings two Alembic migrations (thread labels in 0.92, full-text thread search in 0.93), which the backend applies itself on startup, andhaiku.ragbrings no RAG store migration - docling-serve:
v1.38.0tov1.38.2, the releasehaiku.rag0.107 and later pair docling with - the web client: frontend
0.114to0.117, whose thread labels and thread search need soliplex 0.92 or later, so bump the two together - the image builds bind-mount the requirements files instead of copying them
into
/tmp: aCOPY --linkinto/tmpleaves it mode0755under Docker's containerd image store, the default for new Docker 29 installs, which breaks apt in thesoliplex-devbuild and temporary files at run time - the
soliplex-templatefloor insoliplex-dev/Dockerfileis>=0.22, as rung 9 set it; stacks generated byv0.22orv0.23still say>=0.21 - the session key (
SESSION_MIDDLEWARE_TOKEN) is a generated Docker secret, so sessions survive a backend restart; before, it fell back to a random value on every start - the sample
bare-bonesfilesystem skill gains a body line, sosoliplex-cli auditno longer flags it as having no instructions
Skip the steps that do not apply. Each names what the current template has; compare against a stack the rung's release generates.
-
Stop the stack with
docker compose down, and back up the Postgres databases andrag/db/(see Before you start): this rung migrates both Soliplex databases. -
Bump the releases.
- the
FROMline inbackend/Dockerfile:soliplex-postgres:0.89becomessoliplex-postgres:0.93(and intui/Dockerfile, if the stack ships the TUI,soliplex-tui:0.89becomessoliplex-tui:0.93) - the ingester image in
docker-compose.yml(the&haiku_rag_imageanchor):haiku.rag-slim:0.104.0becomeshaiku.rag-slim:0.112.0 - the
docling-serveimage indocker-compose.yml: thev1.38.0tag becomesv1.38.2(for exampledocling-serve-cpu:v1.38.2) - the
FROMline innginx/Dockerfile:frontend-web:0.114becomesfrontend-web:0.117 - the manifest in
pyproject.toml:soliplex_image_tag = "0.93",soliplex_dev_constraint = ">= 0.93, < 0.94",haiku_rag_version = "0.112.0",docling_serve_version = "v1.38.2", thev1.38.2tag indocling_serve_image, andfrontend_version = "0.117" - the
soliplexrequirement in the root and packagepyproject.tomlfiles:>= 0.93, < 0.94; then runuv lockin each project that has auv.lock(usually the root only)
The two
/v0.114.0+101/examples innginx/nginx.conf's comments become/v0.117.0+106/; nothing else in that file changes. - the
-
Bind-mount the requirements files. In
backend/Dockerfile, remove the lineand add a bind mount to the
RUNstep that reads the file, after its two existing--mountlines:RUN --mount=from=uv,source=/uv,target=/usr/local/bin/uv \ --mount=type=cache,target=/root/.cache/uv \ --mount=type=bind,source=requirements.txt,target=/tmp/requirements.txt \ if grep -qv '^[[:space:]]*\(#\|$\)' /tmp/requirements.txt; then \Do the same in
soliplex-dev/Dockerfileforrequirements-dev.txt: remove itsCOPY --link requirements-dev.txt /tmp/requirements-dev.txtline, and add--mount=type=bind,source=requirements-dev.txt,target=/tmp/requirements-dev.txtto theRUNstep that follows it. The rest of each step is unchanged; the reference stack also carries a short comment above each step saying why the file is mounted.In the same file, check the
soliplex-templatefloor. Rung 9 raised it, but thev0.22andv0.23generators did not, so a stack they generated may still have>=0.21: -
Make the session key a generated secret. In
docker-compose.yml, declare it beside the other.gensecrets at the end of the file:and add
- session_middleware_tokento twosecrets:lists: thebackendservice's, and the one anchored&soliplex_dev_secretsonsoliplex-dev, whichsoliplex-provisionerandstack-initshare. Inbackend/environment/installation.yaml, put afile_pathsource first inSESSION_MIDDLEWARE_TOKEN's list:- secret_name: "SESSION_MIDDLEWARE_TOKEN" sources: - kind: "file_path" file_path: /run/secrets/session_middleware_token - kind: "env_var" env_var_name: "SOLIPLEX_SESSION_MIDDLEWARE_TOKEN" - kind: "random_chars"Then generate the new secret; the script writes only missing files:
Sessions signed with the old random key end once more when the backend first starts with this one.
-
Give the sample skill a body. If the stack still has the generated
backend/environment/skills/bare-bones/SKILL.md, add a line after its closing---: -
Check the configuration you changed by hand. The generated files need nothing more, but soliplex 0.91 to 0.93 refuse some older spellings:
installation.yaml: the top-levelthread_persistence_dburi:andauthorization_dburi:stanzas are gone (since 0.91); usethread_persistence_db:andauthorization_db:, each withsync_dburiandasync_dburi- room and agent configs: a
system_promptorlogo_imagefile must resolve inside the config's own directory (since 0.92) - OIDC providers:
accepted_azp_liststill loads, but is deprecated in favor ofaccepted_client_idsand goes away after 0.94 haiku.raghooks and metadata providers: from 0.112, onlyedit_documentwrites a document'smetadata["user"]; auserkey set anywhere else is dropped
-
Rebuild the images, the profiled
soliplex-devandstack-initincluded:docker compose uppulls the new ingester and docling-serve images itself. -
Check the databases. The Soliplex databases are behind by the two migrations above; with the default configuration the backend applies them when it starts. To see what is owed first:
A stack that configured a migration policy drives its own migrations; see the migrations reference. The RAG stores need nothing: no
haiku.ragrelease since 0.91 changed their layout, so this should report nothing to migrate:One exception:
haiku.rag0.112 no longer upgrades a store recorded before 0.64. A stack that has run its migrations at every rung has none; if--checkreports one, migrate it withhaiku.rag0.111.1 first, as the error message says. -
Start the stack with
docker compose up -d, then Check it, and commit. The audit's secrets section should listSESSION_MIDDLEWARE_TOKEN OK (file_path); withrandom_charsinstead, it also warns that the value changes on every restart, which means step 4 is incomplete.