Package Radicale for the Umbrel App Store

[salmonumbrella]

Would you be open to publishing Radicale in the official Umbrel App Store?

Radicale seems like a particularly good fit for Umbrel: it is lightweight, self-hosted, and provides CalDAV/CardDAV for a private home server. The project already publishes the multi-architecture ghcr.io/kozea/radicale:stable image, and the existing Compose definition separates persistent config and data volumes.

The use case is to run a durable calendar and contact server on Umbrel and access it privately over LAN or Tailscale. Umbrel app submissions are made through getumbrel/umbrel-apps.

I would be happy to help prepare and test the Umbrel package if the maintainers are open to an official listing. Would you prefer a community-maintained submission, or should the packaging be maintained under the Radicale project?

[pbiering]

@gentooboontoo @liZe @kalsi-avneet - any opinion?

[kalsi-avneet]

I'm not familiar with Umbrel, but from the request I understand that existing docker package can be used as-is.

I would be happy to help prepare and test the Umbrel package if the maintainers are open to an official listing

@salmonumbrella, could you tell if any change to the existing docker image would be needed, and what would "official listing" mean?

[salmonumbrella]

It just means a submission to the app store like this.

[kalsi-avneet]

It just means a submission to the app store like this.

Thank you for the reply.

I could understand that the submission process involves raising a PR with the compose file and other manifests.

I would like your help to understand the difference between :

1. community-maintained submission, and
2. packaging maintained under the Radicale project,

With respect to changes required in the current repository

[salmonumbrella]

No changes to this repository are needed in either case. The existing multi-arch ghcr.io/kozea/radicale:stable image is used as-is, and all packaging files (the umbrel-app.yml manifest, a docker-compose.yml, icon and gallery assets) live in the getumbrel/umbrel-apps repo, not here.

The difference is only who submits and maintains the store entry:

1. Community-maintained — I open the PR to umbrel-apps and am listed in the manifest's submitter field. When Radicale releases a new version, I open a small follow-up PR bumping the version and the pinned image digest. Zero ongoing work for the Radicale maintainers.
2. Maintained under the Radicale project — same files, but the project is listed as the submitter and someone from the project handles the version-bump PRs.

[kalsi-avneet]

@salmonumbrella,

Thank you for the reply. I understood both cases from your explanation.

Regarding support, in future if a user needs Umbrel environment specific support, would it be ok to request you to assist?