From c010099dae8f132c0a02d4511c2d63b2dc5cf9d1 Mon Sep 17 00:00:00 2001 From: Gabriel Radureau Date: Mon, 29 Jun 2026 07:54:01 +0200 Subject: [PATCH] docs(test): preserve the install.lock step in test/README MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The pre-existing (untracked) test/README documented creating Dolibarr's install.lock after a fresh install — a non-obvious operational step missing from the rewritten README. Preserve it (generalized to the per-env namespace/label, with a note that a prod-seeded instance doesn't need it). Co-Authored-By: Claude Opus 4.7 (1M context) --- test/README.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/test/README.md b/test/README.md index 02c09d7..185d1e7 100644 --- a/test/README.md +++ b/test/README.md @@ -25,6 +25,22 @@ Copy `.env.example` to `.env` and fill it in. `.env`, `*.key`, and cp .env.example .env ``` +## Lock the installer (after a fresh install via `main.ts`) + +Dolibarr keeps its web installer reachable until an `install.lock` file exists. +After a fresh install (the `main.ts` flow), create it in the target pod — for the +sandbox: + +```sh +kubectl -n erp-sandbox exec \ + "$(kubectl get pod -n erp-sandbox -l app.kubernetes.io/instance=erp-sandbox -o name)" -- \ + /bin/sh -c 'touch /var/www/html/install.lock && chown www-data:www-data /var/www/html/install.lock' +``` + +For prod, swap to `-n erp -l app.kubernetes.io/instance=erp`. Not needed when the +instance was seeded from a prod dump instead of freshly installed — see +`../ops/sandbox/`. + ## Provision the sandbox Provisions `erp-sandbox.arcodange.lab`: enables the REST API module, creates the -- 2.49.1