simple CalDAV calendar server
Project homepage: https://radicale.org/
Description
Radicale is a small but powerful CalDAV (calendars, to-do lists) and
CardDAV (contacts) server, that:
- Shares calendars and contact lists through CalDAV, CardDAV and HTTP.
- Supports events, todos, journal entries and business cards.
- Works out-of-the-box, no complicated setup or configuration required.
- Offers flexible authentication options (including Dovecot SASL).
- Can limit access by authorization.
- Can secure connections with TLS.
- Works with many CalDAV and CardDAV clients.
- Stores all data on the file system in a simple folder structure.
- Can be extended with plugins.
Package information
- Ports path
- productivity/radicale
- Package architecture
- amd64
- Maintainer
- The OpenBSD ports mailing-list <ports@openbsd.org>
- Categories
- productivity, net, lang/python
- Available flavors
- None listed
- Only for architectures
- aarch64, amd64, arm, i386, mips64, mips64el, powerpc, powerpc64, riscv64, sparc64, alpha, hppa
Ports list build and test dependencies as well as runtime dependencies. pkg_add selects those needed for installation.
Direct dependencies
Runtime
Build
- lang/python/3
- devel/py-build
- devel/py-installer
- devel/py-setuptools py3-setuptools->=79v0
- devel/py-wheel
Test
- www/py-waitress
- security/py-bcrypt
- security/py-argon2-cffi
- databases/py-ldap3
- textproc/py-defusedxml
- security/py-passlib
- textproc/py-vobject
- net/py-pika
- www/py-requests
- lang/python/3
- devel/py-test
OpenBSD README
This README contains unresolved ports variables; replace them before using its commands.
+-----------------------------------------------------------------------
| Running radicale on OpenBSD
+-----------------------------------------------------------------------
Authentication
==============
To enable simple passwords, edit ${SYSCONFDIR}/radicale/config and change
"#type = denyall" to
"type = htpasswd".
By default calendars may only be accessed by their owner. To adjust
the rights for calendars please refer to the
${SYSCONFDIR}/radicale/rights file and the upstream documentation on
"Authentication and Rights".
For further authentication options, consult Radicale's documentation.
Previous users of Radicale with more complex authentication setup
should be aware that only none/htpasswd are provided as standard;
plugins are required for others.
Encryption
==========
To enable encryption with the internal web server, change "ssl = False"
to "ssl = True" in ${SYSCONFDIR}/radicale/config, and install a certificate
and key in the files named in "certificate" and "key". (They need to be
readable by the _radicale user, so the common location in /etc/ssl/private
won't work). Alternatively run HTTP on localhost and proxy from alternative
web server software.
Upgrading from Radicale 2 to 3
==============================
There are many changes from Radicale 2.x to 3.x, see the following upgrade
checklist from CHANGELOG.md. Refer to the documentation for more details.
Config
Some settings were removed
The default of auth.htpasswd_encryption changed to md5
The setting server.realm moved to auth.realm
The setting logging.debug was replaced by logging.level
The format of the rights.file configuration file changed:
Permission r replaced by Rr
Permission w replaced by Ww
New permission i added as subset of r
Replaced variable %(login)s by {user}
Removed variable %(path)s
{ must be escaped as {{ and } as }} in regexes
File system storage
The storage format is compatible with Radicale 2.x.x
Run radicale --verify-storage to check for errors
Custom plugins:
auth and web plugins require minor adjustments
rights plugins must be adapted to the new permission model
storage plugins require major changes