automx: the schema its seed writes belongs to one automx2, so that one is named

An unpinned pip install took the latest automx2, whose schema grew a
column (server.prio) the module's own seeding SQL predates — a 500 on
every autoconfig request against a table the seed had just written.
2021.6 is what the proven image runs; the seed and the software agree
again. Regenerating the seed for a newer automx2 is its own change,
made deliberately, not by whatever pip resolved this week.
This commit is contained in:
2026-09-25 23:59:42 +02:00
parent b8a50ee7a0
commit 30b7ce429c
+1 -1
View File
@@ -19,7 +19,7 @@ RUN chmod u+x setupvenv.sh start add-domains setup setup-db
RUN ./setupvenv.sh \ RUN ./setupvenv.sh \
&& . .venv/bin/activate \ && . .venv/bin/activate \
&& pip install automx2 && pip install automx2==2021.6
# The launcher `start` expects. In the predecessor's image this wrapper appeared during a build # The launcher `start` expects. In the predecessor's image this wrapper appeared during a build
# step that never made it into the files this module carries — the image worked and the recipe # step that never made it into the files this module carries — the image worked and the recipe