Paul Payne
4d983819c9
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
876 B
876 B
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".
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 10–15 minutes
Use a startupProbe with a long window to prevent premature restarts:
startupProbe:
failureThreshold: 40
periodSeconds: 30 # up to 20 minutes total
Once the startup probe passes, regular liveness/readiness probes with initialDelaySeconds: 0
take over.