# Self-host Radicale

> Calendar (CalDAV) and contacts (CardDAV) server. One user is created at first boot with a generated password (visible in the service environment settings, never on a process command line); it is stored as a SHA-512 hash in /var/lib/radicale/users and each user only sees their own collections. Add users by appending htpasswd lines to that file.

- Page: https://levelrail.com/templates/radicale/
- JSON: https://levelrail.com/templates/radicale.json
- Category: Productivity
- Licence: GPL-3.0-or-later (Copyleft license)
- Source: https://github.com/Kozea/Radicale
- Upstream docs: https://radicale.org/v3.html

## Requirements
- Memory: about 128 MiB
- amd64: published, arm64: tested
- Needs configuration before start: no
- Pinned image tag: 3.9.0

## Services

| Service | Image | Tag | Ports | Volumes |
| --- | --- | --- | --- | --- |
| radicale | kozea/radicale | 3.9.0 | 5232 | data -> /var/lib/radicale |

## Environment

| Service | Variable | Kind |
| --- | --- | --- |
| radicale | RADICALE_PASSWORD | generated |
| radicale | RADICALE_USER | generated |

## Deploy

### CLI

```bash
levelrail-cli templates deploy radicale --name my-radicale
```

### API

```bash
curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/radicale/deploy
```

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

## Questions

### Can I deploy Radicale on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Radicale, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image kozea/radicale:3.9.0 is what you deploy there.

Self-host Radicale, Radicale docker compose file, deploy Radicale on a VPS: this page lists the pinned image, ports, volumes and the commands for each.
