docs: test moves to its own native VM as well; docker-1 keeps CI (Gitea issue 37)

Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-10-27 15:16:07 -06:00
parent d9aab10987
commit 226f505648
4 changed files with 6 additions and 6 deletions
@@ -8,7 +8,7 @@ All notable changes to this project are recorded here. The format follows [Keep

 - Gitea issues 10, 14, 15, 16, 22, 26, 28 and 29: SethD kept the built rules (cancelled work orders flagged only, data book date for Clerical and Q.C., signature undo rules, the server release gate, no "copy marks" button, block signature removal, the data book built at filing, every role may read the PDFs). Nothing changes in the build.
 - Gitea issue 6: every policy tightening stays, filing for packets routed to Shipping included.
- Gitea issue 37: production runs natively on its own Linux VM, not in Docker on docker-1. The test stack and CI stay on docker-1. Built in phase 10.
+- Gitea issue 37: production and test each run natively on their own Linux VM, not in Docker. docker-1 keeps CI only. Built in phase 10; the docker-1 test stack runs until the test VM is ready.
 - Gitea issue 7: project files are also archived to an NFS share on the QNAP. Phase 10 adds an Admin setting for the archive folder that checks read and write. Nothing is deleted from Packet Station.
 - Gitea issue 2: a PIN is enough for every sign-off, Q.C. accept and filing included. Nothing changes in the build.
 - Gitea issue 3: shop devices keep the registered-device cookie. No device certificate is planned.