3 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	de809d7e0a	Keep the store's superuser file in the postgres module's own directory, not in /var/lib/postgres (issue 1873) ... The postgres module's own secrets move from /var/lib/postgres, the postgresql package's directory, to its directory under /var/lib/mesh (mesh-catalog, fix/1873-system-state-dirs). Genesis writes the store's superuser file at the module's own-secret path, so the store it raises is the one the module adopts in place: StoreSuperuserFile follows, to /var/lib/mesh/postgres/superuser.secret. A directory genesis makes on the way is 0755, the mode of the mesh's directories, and only the credential's own is 0700: MkdirAll at 0700 would have closed /var/lib/mesh on a machine that had none yet.	2026-10-22 21:36:38 +02:00
mesh-tools	52600ec7bd	Take the node-engine's parser from mesh-sdk: remaining imports (issue 1392)	2026-10-20 11:17:14 +00:00
jochen	4dde21f0ab	Raise genesis's store as the postgres module's server, so the store step adopts it as it runs (hq issue 609, ADR 0338) ... The bundle raised the store as mesh-store, on upstream postgres, in a docker volume; the postgres module keeps it as postgres, on its pgvector image, in /var/lib/mesh-store owned 999:70, reading its superuser password from a file. The store step refused, and genesis stopped at step 17 of 24. The bundle now raises the store with the module's name, image, data directory and password file, and every step of the bundle and the installer reaches it by that name. The refusal to raise a store over data it cannot open looks for a cluster in the store's directory, no longer for the old volume.	2026-10-13 10:47:53 +02:00