Hi everyone

I’m trying to degoogle as much as possible. I’ve heard about this thing called calDAV and cardDAV but I have no idea how to use it.

With radicale, do I need to install some other somewhere in order to use it?

I’m just looking for basic useage for myself only at this stage. I’d like to be able to self host my own calendar and contacts. Is radicale appropriate for this?

Is it safe to self host a calendar?

Can a self hosted calendar still send and receive invites to other calendars?

Any help greatly appreciated, thank you

  • Ooops@feddit.orgEnglish
    1·
    4 hours ago

    Take a look at the config file (/etc/radicale/config). It’s extensively commented. Although you barely need to change any defaults for regular use.

    Just create an htpasswd file (with htpsswd, apache-tools or just any of the one million available online generators) and edit two lines under [auth] to read type = htpasswd and htpasswd_filename = <the location and file you created>.

    And you can start (and enable) Radicale via the systemd service usually included in the installed package. (Or for early testing just start the server manually… radicale starts it with the defaults from the config file. You can also configure everything with parameters but that’s an insanely long list (radicale --help if you are interested in seeing them)…)

    The webinterface to login will be available (by default settings) under http://localhost:5232/.

    All you have to do then is change the config so Radicale listens on the server’s IP instead so it’s available in in your network. (Plus the usual stuff of making it available from the outside if you need that like for any other sevice)

    And any calendar/contact software will bring a wizard that guides you through the process of sync’ing, usually just asking for an address to reach your server, as well as user and password.

    EDIT: I looked up the defaults and you can skip all the autehntification stuff in the beginning. By default just anyone can access the webpage at port 5232. So you can just test it and only bother with authentication later (definitely when you plan to make it available from the outside, for example to sync phones).