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
28 lines
1.2 KiB
Markdown
28 lines
1.2 KiB
Markdown
# Moodle — Notes
|
||
|
||
## No official Docker image — Bitnami is the standard
|
||
|
||
The Moodle project does not publish an official Docker image. `bitnamilegacy/moodle` is the
|
||
widely-used standard and is the basis for the official Bitnami Helm chart. The `WC-BITNAMI`
|
||
warning is suppressed in `app.yaml` because there is no viable alternative.
|
||
|
||
Note: Bitnami images require Docker Hub authentication since 2023. Ensure the cluster has
|
||
Docker Hub credentials configured if pull rate limits or auth errors appear.
|
||
|
||
## Bitnami filesystem layout
|
||
|
||
Bitnami images store persistent data under `/bitnami`. The PVC is mounted at `/bitnami` to
|
||
cover both Moodle files and any Bitnami-managed config. Do not change the mount path without
|
||
also adjusting Bitnami's internal configuration.
|
||
|
||
## MySQL-only
|
||
|
||
Moodle's `MOODLE_DATABASE_TYPE=mysqli` requires MySQL/MariaDB. PostgreSQL is not supported.
|
||
The deployment uses Wild Cloud's MySQL dependency (`requires: [mysql]`).
|
||
|
||
## Long first-run initialization
|
||
|
||
Moodle runs database migrations and installs core plugins on first startup, which can take
|
||
5–15 minutes. The `startupProbe` is configured with a long timeout (`failureThreshold: 240`,
|
||
`periodSeconds: 15` = up to 60 minutes) to accommodate this.
|