fix: container sets up its own data directory (closes #75)
check / check (push) Successful in 49s

bin/entrypoint.sh, still running as root, now creates DATA_DIR if
missing and gives it and /data to the netwatch user with mode 750
before starting the backend as that user. An empty host directory
owned by root, or one holding files from another uid, works with no
step on the host, so the README no longer tells the operator to create
or chown it. The image no longer sets that ownership at build time.

Model: opus-5-5
This commit is contained in:
2026-09-29 09:16:58 +00:00
parent c226ceee01
commit 7d31f514e3
5 changed files with 24 additions and 14 deletions
+7
View File
@@ -23,6 +23,13 @@ latest run passes.
# Completed Steps
- 2026-09-29: the container sets up its own data directory (issue #75):
`bin/entrypoint.sh`, still as root, creates `DATA_DIR` if missing and gives it
and `/data` to the `netwatch` user with mode 750 before starting the backend
as that user, so an empty host directory owned by root, or one holding files
from another uid, works with no step on the host. The `README.md` first-run
step that created and chowned the host directory is gone, and the image no
longer sets that ownership at build time
- 2026-09-29: `backend/.golangci.yml` re-vendored from `sneak/prompts` (issue
#41): `gomodguard`, deprecated in golangci-lint v2.12.0, is disabled and its
successor `gomodguard_v2` enabled with the org block list, so lint runs print