feat(supabase): add services and statefulset for database management

feat(synapse): update ingress to use traefik ingress class and bump version

feat(syncthing-discovery): introduce syncthing discovery service with deployment and ingress

feat(syncthing-relay): add syncthing relay server with deployment and ingress configuration

fix(taiga): update liveness and readiness probes to use tcpSocket for health checks

fix(taiga): change PVC access mode to ReadWriteMany for media and static storage

feat(traefik): add icon and ignore rules for traefik service

docs(ushahidi): add notes for Redis configuration and Laravel startup probe adjustments

feat(ushahidi): implement dedicated Redis deployment for Ushahidi

fix(vllm): update deployment strategy and readiness/liveness probes for improved stability

fix(writefreely): pin writefreely image version to v0.15.1 for consistency

docs(zulip): add notes for TLS-terminating reverse proxy configuration and expected behavior
This commit is contained in:
2026-07-02 21:34:27 +00:00
parent 9f5057dff8
commit 4d983819c9
151 changed files with 3403 additions and 1303 deletions

27
odoo/notes.md Normal file
View File

@@ -0,0 +1,27 @@
# Odoo — Notes
## Explicit database name and `-i base` required on first run
The official Odoo Docker image does not auto-initialize the database. Without specifying the
database name and installing the base module, Odoo starts in multi-database manager mode and
health checks fail with "Database not initialized".
```yaml
args: ["-d", "DATABASE_NAME", "-i", "base"]
```
The `-i base` flag installs Odoo's base module and creates all database tables on first run.
Subsequent runs with `-i base` are safe — it updates rather than reinstalls.
## First-run initialization takes 1015 minutes
Use a `startupProbe` with a long window to prevent premature restarts:
```yaml
startupProbe:
failureThreshold: 40
periodSeconds: 30 # up to 20 minutes total
```
Once the startup probe passes, regular liveness/readiness probes with `initialDelaySeconds: 0`
take over.