Problem
support_radicale capability defaults to true, showing Calendar menu even when Radicale is not deployed.
Users see: "The calendar is not yet configured on your system, in order to learn how to enable click here" - but regular users cannot configure server-side services.
Current Behavior
docker-compose.yml does not map FRONTEND_DISABLE_RADICALE
- Backend default:
disable_radicale: false → Calendar visible
- Without
radicale/radicale.yml in COMPOSE_FILE → broken UX
Expected Behavior
Calendar menu should only appear when Radicale is actually deployed.
Suggested Fix
docker-compose.yml:
FRONTEND_DISABLE_RADICALE: "${FRONTEND_DISABLE_RADICALE:-true}"
radicale/radicale.yml:
services:
opencloud:
environment:
FRONTEND_DISABLE_RADICALE: "false"
This way:
- Default (no Radicale): Calendar hidden
- With
radicale.yml: Calendar visible and functional
Related
Problem
support_radicalecapability defaults totrue, showing Calendar menu even when Radicale is not deployed.Users see: "The calendar is not yet configured on your system, in order to learn how to enable click here" - but regular users cannot configure server-side services.
Current Behavior
docker-compose.ymldoes not mapFRONTEND_DISABLE_RADICALEdisable_radicale: false→ Calendar visibleradicale/radicale.ymlinCOMPOSE_FILE→ broken UXExpected Behavior
Calendar menu should only appear when Radicale is actually deployed.
Suggested Fix
docker-compose.yml:
radicale/radicale.yml:
This way:
radicale.yml: Calendar visible and functionalRelated
disable_radicale)