Merge pull request 'fix(deploy): push through a TLS-terminating proxy, not raw Gitea HTTP' (#8 ) from fix/deploy-registry-tls into fix/deploy-unraid-template-port

Reviewed-on: #8
2026-09-21 20:59:14 -04:00
1 changed files with 0 additions and 7 deletions
@@ -63,13 +63,6 @@ the same values, there's no separate migration-time config anymore (docs/DECISIO
 |---|---|
 | `/data` | The SQLite database file. Will also hold the content-addressed blob store once Phase 1 builds ingestion. This is the only thing that needs backing up. |

-The container runs as a fixed non-root user (uid/gid `999`), not root and not Unraid's usual
-`nobody:users` (99:100). If `/data`'s host directory doesn't already exist, Docker/Unraid creates
-it owned by `nobody:users` with no write access for other users — the container starts, but
-uvicorn fails immediately with `sqlite3.OperationalError: unable to open database file`, since it
-can't create the SQLite file inside a directory it can't write to. Fix once, before first start:
-`chown -R 999:999 <host path>` (e.g. `/mnt/user/appdata/velodrome` on Unraid).
-
 ## Unraid

 Import `unraid-template.xml` from the Docker tab's "Add Container" template picker — it exposes