Move to soliplex 0.86.1 and haiku.rag 0.101.0
Part of Upgrading an existing stack.
Walk this rung with the v0.19b1 skill release — its generator produces the rung's end state (soliplex 0.86.1 on the release images, with haiku.rag 0.101.0). 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.
-
Stop
backendandhaiku-ingester, and back up the Postgres databases andrag/db/before upgrading. -
Adopt the image-shape changes, which came to the template ahead of this step: the image shim Dockerfiles (
haiku.rag/Dockerfile,docling-serve/Dockerfile) are gone; their build recipes moved toREADME.mdfiles beside their build contexts, and the template'sbuild:stanzas for those services ship commented. Delete your copies (or rename them to theREADME.mds, which carry the recipes), and comment the stanzas the same way. -
Set the backend and optional TUI image tags to
0.86.1; set the haiku.rag image to0.101.0in thehaiku_rag_imageanchor indocker-compose.yml; set thedocling-serveimage toquay.io/docling-project/docling-serve-cpu:v1.38.0. -
Update
soliplex_image_tag,haiku_rag_version, andsoliplex_dev_constraintin the project's manifest. Use>= 0.86.1, < 0.87for the Soliplex requirement in the root and packagepyproject.tomlfiles, then runuv lockin each project. -
In
haiku.rag/haiku.rag.yaml, move the source list fromingester.sourcesto thesourceslist of theingester.databasesentry keyedhaiku.rag(the key is the database's own name, dot included). Keep its source ids and paths. Addnamespace: soliplexunderingester.queue. This still writes/data/haiku.rag.lancedb. Additional databases are described in RAG pipeline. -
In the
haiku-ingesterCompose command, changesh -ctosh -ecand insert this command after exportingINGESTER_DB_PASSWORDand beforeexec haiku-ingester --config /app/haiku.rag.yaml serve: -
Rebuild
backend,soliplex-dev,haiku-ingester,docling-serve, and the optionaltuiwithdocker compose build --pull. -
Before restarting the ingester, follow the queue migration to migrate the schema and assign existing rows to
soliplex. Otherwise the ingester will not see its previous jobs and sync state. The template prepares the queue schema before every ingester start. Manual namespace assignment is needed only when upgrading rows from a queue without namespaces. -
The ingester's new database API is
GET /databases/{name}; update any callers ofGET /databaseto follow suit. -
Run
uv run scripts/migrate_soliplex_dbs.py --checkanduv run scripts/migrate_rag_dbs.py --check; apply any reported migrations with the relevant service stopped. Start the stack withdocker compose up -dand inspect the backend and ingester logs. Then Check it, and commit.