From 95f79129479f43e2970d1d0481c81e7852bbded8 Mon Sep 17 00:00:00 2001
From: Lennart <18233294+lennart-k@users.noreply.github.com>
Date: Wed, 15 Jan 2025 18:11:07 +0100
Subject: [PATCH] Update README.md, mention WebDAV Push configuration

---
 README.md | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/README.md b/README.md
index 998a50c..8891c0c 100644
--- a/README.md
+++ b/README.md
@@ -66,6 +66,17 @@ Since it's sensitive information, the secure but slow hash algorithm `argon2` is
 I recommend to generate random app tokens for each CalDAV/CardDAV client.
 These can use the faster `pbkdf2` algorithm.
 
+### WebDAV Push
+
+RustiCal supports [WebDAV Push](https://github.com/bitfireAT/webdav-push/) which can notify compatible clients like DAVx5 about changed calendar/addressbook objects.
+Since push messages are currently not encrypted you might potentially want to ensure that users only subscribe through your push server (e.g. [ntfy.sh](https://ntfy.sh/)), you can configure it the following:
+
+```toml
+[dav_push]
+# Must strictly be the URL origin (so no trailing slashes)
+allowed_push_servers = ["https://your-instance-ntfy.sh"]
+```
+
 ## Relevant RFCs
 
 - Versioning Extensions to WebDAV: [RFC 3253](https://datatracker.ietf.org/doc/html/rfc3253)