DAV is All You Need

2022-01-01  •  (Updated 2022-06-03)  •  Contacts, calendars, passwords, oh my!

This post is part of a series:
Previously: Managing a Home Server With Nix
Next: The Case for Open Infrastructure

For some time now I've been trying to find an alternative solution to Google Keep for shared note taking. The motivation for this change was two-fold:

So this weekend I buckled down and actually made the switch. The first step was to find something to switch to, however, which ended up being not trivial. There's a million different options in this space, but surprisingly few which could fulfill the exact niche we need in our household:

I've already got a Nextcloud instance running at home, and there is certainly a notes extension for it, so that could have been an option here. But Nextcloud very much does not fall into the second point above: it's not simple. It's a giant PHP app that uses Postgres as a backend, has its own authentication and session system, and has a plugin system. Frankly, it was easily the biggest security hole on the entire server, and I wasn't eager to add usage to it.

Happily, I found another solution.


There's a project called Joplin which implements a markdown-based notes system with clients for Android, iPhone, Linux, Mac, and Windows. Somewhat interestingly there is not a web client for it, but on further reflection I don't think that's a big deal... no bloated javascript frameworks to worry about at least.

In addition to their own cloud backend, Joplin supports a number of others, with the most interesting being WebDAV. WebDAV is an XML-based extension to HTTP which allows for basic write operations on the server-side, and which uses HTTP's basic auth for authentication. You can interact with it using curl if you like, it really can't get simpler.

Caddy is the server I use to handle all incoming HTTP requests to my server, and luckily there's a semi-official WebDAV plugin which adds WebDAV support. With that compiled in, the Caddyfile configuration is nothing more than:

hostname.com {

    route {

        basicauth {
            sharedUser sharedPassword

        webdav {
            root /data/webdav



With that in place, any Joplin client can be pointed at hostname.com using the shared username/assword, and all data is stored directly to /data/webdav by Caddy. Easy-peasy.


Where WebDAV is an extension of HTTP to allow for remotely modifying files genearlly, CardDAV and CalDAV are extensions of WebDAV for managing remote stores of contacts and calendar events, respectively. At least, that's my understanding.

Nextcloud has its own Web/Card/CalDAV service, and that's what I had been, up till this point, using for syncing my contacts and calendar from my phone. But now that I was setting up a separate WebDAV endpoint, I figured it'd be worth setting up a separate Card/CalDAV service and get that much closer to getting off Nextcloud entirely.

There is, as far as I know, no Card or CalDAV extension for Caddy, so I'd still need a new service running. I came across radicale, which fits the bill nicely. It's a simple CalDAV and CardDAV server which saves directly to disk, much like the Caddy WebDAV plugin. With that running, I needed only to add the following to my Caddyfile, above the webdav directive:

handle /radicale/* {

    uri strip_prefix /radicale

    reverse_proxy {
        header_up X-Script-Name /radicale


Now I could point the DAVx5 app on my phone to hostname.com/radicale and boom, contact and calendar syncing was within reach. I did have a lot of problems getting DAVx5 working properly, but those were more to do with Android than self-hosting, and I eventually worked through them.


At this point I considered that the only thing I was still really using Nextcloud for was password management, a la Lastpass or 1Password. I have a lot of gripes with Nextcloud's password manager, in addition to my aforementioned grips with Nextcloud generally, so I thought it was worth seeing if some DAV or another could be the final nail in Nextcloud's coffin.

A bit of searching around led me to Tusk, a chrome extension which allows the chrome browser to fetch a KeePassXC database from a WebDAV server, decode it, and autofill it into a website. Basically perfect. I had only to export my passwords from Nextcloud as a CSV, import them into a fresh KDBX file using the KeePassXC GUI, place the file in my WebDAV folder, and point Tusk at that.

I found the whole experience of using Tusk to be extremely pleasant. Everything is very well labeled and described, and there's appropriate warnings and such in places where someone might commit a security crime (e.g. using the same password for WebDAV and their KDBX file).

My one gripe is that it seems to be very slow to unlock the file in practice. I don't think this has to do with my server, as Joplin is quite responsive, so it could instead have to do with my KDBX file's decryption difficulty setting. Perhaps Tusk is doing the decryption in userspace javascript... I'll have to play with it some.

But it's a small price to be able to turn off Nextcloud completely, which I have now done. I can sleep easier at night now, knowing there's not some PHP equivalent to Log4j which is going to bite me in the ass one day while I'm on vacation.

If you liked this post, consider checking out other posts in the series:
Previously: Managing a Home Server With Nix
Next: The Case for Open Infrastructure