Installation
Docker
You can start a RustiCal container using the following command:
docker run \
-p 4000:4000 \
-v YOUR_DATA_DIR:/var/lib/rustical/ \
-v OPTIONAL_YOUR_CONFIG_TOML:/etc/rustical/config.toml \ # (1)!
-e RUSTICAL__CONFIG_OPTION="asd" \ # (2)!
ghcr.io/lennart-k/rustical
- Mount config file
- Alternatively specify configuration using environment variables
User management
In case you already have an OIDC server set up, see here how to set up OIDC login and maybe skip this section.
Otherwise you will have to use the rustical principals command.
In Docker you can run this with
docker run --rm -it -v YOUR_DATA_DIR:/var/lib/rustical/ ghcr.io/lennart-k/rustical rustical principals
This is also the place to set up groups.
Groups and rooms are also just principals and you can specify them as such using the --principal-type parameter.
To assign a user to a group you can use the rustical membership command. Being a member to a principal means that you can completely act on their behalf and see their collections.
Note: Many clients don’t support autodiscovery of principals a user is a member of. In that case you’d have to set up multiple CalDAV profiles in your client with the respective principal URLs.
Password vs app tokens
The password is optional (if you have configured OpenID Connect) and is only used to log in to the frontend.
Since it’s sensitive information, a secure but slow hash algorithm (argon2) is chosen.
App tokens are used by your CalDAV/CardDAV client (which can be managed through the frontend).
I recommend to generate random app tokens for each CalDAV/CardDAV client.
Since the app tokens are random they use the faster pbkdf2 algorithm.