Clock applet multiple data sources

[oz123]

Building on top of the work for getting events from EDS, I added the option to read events from vdir.

This is useful for people who don't want to install evolution just for getting calendar events shown in the applet. Also, it requires less RAM (no background process, as vdirsyncher can be launched using cron or a systemd user unit files).

This is my 3rd attempt to implement this feature (previous attempts not published), I hope this time I got it right,

[lukefromdc]

I do not know how to use vdirsyncer, I normally use text files on the desktop to manage events (primitive but hard to forget) so without a gui option to invoke it from the clock, I was unable to test that functionally. Didn't interfere with Evolution, though I have an empty calendar so obscure problems might not show up.

The line
password = "yourpassword"
in the example config file is a security hazard if users are supposed to store their login password (which gives ROOT access if they have sudo allowed!) in it!

Without it, on running
vdirsyncer discover my_calendar

I get

Discovering collections for pair my_calendar
my_local:
warning: Failed to discover collections for my_remote, use `-vdebug` to see the full traceback.
error: Unknown error occurred: Cannot connect to host your-caldav-server:443 ssl:default [Name or service not known]
error: Use `-vdebug` to see the full traceback.
luke@ubuntu:~$ vdirsyncer discover my_calendar -vdebug
Usage: vdirsyncer discover [OPTIONS] [PAIRS]...
Try 'vdirsyncer discover -h' for help.

vdirsyncer sync asks me to run the previous command, and no change seen anywhere in the calendar.

[oz123]

Thanks for testing!
Ok, vdirsyncher is confusing.
I will update the documentation of getting started with it.
As for storing the password -
First, the files should be saved with chmod 600 ( or by setting umask. Both are actually steps that are overlooked or easily forgotten. We can add it too. Additionally, vdirsyncher supports password.fetch` so users running gnome-keyring can do:

$ keyring set mycalendar.com myuser
>TypePasswordinPrompt

Then in the configuration:

[storage foo]
type = "caldav"
url = "https://mycalendar.com/dav/"
username = "myuser"
password.fetch = ["command", "keyring", "get", "mycalendar.com/", "myuser"]

It replicates vdirsyncher documentation in here, but it's going to spare a few minutes for users of mate desktop and make it more secure. I can add it too.

[lukefromdc]

For test purposes, is there any way to set this up to run without calling the user's password at all? If not, being able to prompt for it and not retain it should be enough BUT it remains an unnecessary risk. No guarantee I will be able to test this for function given the complexity of doing so. After all, if the calendar is sensitive the whole /home directory needs to be encrypted.