Differences

This shows you the differences between two versions of the page.

--- owncloud [21.03.2017 06:21] – [synchronize external caldav and carddav sources] Pascal Suter
+++ owncloud [16.07.2021 00:30] (current) – [synchronize external caldav and carddav sources] Pascal Suter
@@ Line 119: / Line 119: @@
 ===== synchronize external caldav and carddav sources =====
+**UPDATE** I have moved away from python virtualenv as it broke vdirsyncer on almost every os update. I now run vdirsyncer in a docker container based on [[https://github.com/kaergel/docker-vdirsyncer]]. Basically copy the tempalte for the ''docker-compose.yml'' file and adjust to your needs. the ''config'' volume is a single file, so if you have multiple calendars to sync, put them all in one file and then pass this file as ''/config'' volume. I also added a directory which is mounted as volume to ''/status'' and used ''/status'' in the ''general'' section of my config file for the status directory. this seems to work fine.
 **caution** this has only been done one-way, so that an external calender which is only changed externally gets regularly synced to owncloud. i haven't tired this in a two way mode.
@@ Line 127: / Line 129: @@
   pip install pipsi
   pipsi --home /opt/owncloud/ install --python python3 vdirsyncer
+  mkdir /opt/owncloud/vdirsyncer/status
+  chmod 777 /opt/owncloud/vdirsyncer/status
 now it's time to configure your vdirsyncer.. in my case i wanted to sync a html read-only source (ical format) to owncloud. here is my config file:
 <code>
 [pair photokiste]
-a = photokiste_crm
+a = "photokiste_crm"
-b = photokiste_owncloud
+b = "photokiste_owncloud"
 collections = null
-conflict_resolution = a wins
+conflict_resolution = "a wins"
 [storage photokiste_crm]
-type = http
+type = "http"
-url = https://www.source-server.com/ical.ics
+url = "https://www.source-server.com/ical.ics"
 [storage photokiste_owncloud]
-type = caldav
+type = "caldav"
-url = https://my.owncloud.server/remote.php/dav/calendars/username/calenarname
+url = "https://my.owncloud.server/remote.php/dav/calendars/username/calenarname"
-username = myuser
+username = "myuser"
-password = mysecret
+password = "mysecret"
 </code>
 the owncloud calendar name can be viewed by hovering over the calendar. it will appear as mouse pointer tooltip.
@@ Line 154: / Line 158: @@
 this might be an onwcloud problem, as owncloud exports the "wrongly" specified events but it does not show them on the web-interface.. so maybe the web ui is just messing this up..
-once the config file is written, vdirsyncer can be run through cron or manually like this:
+once the config file is written, vdirsyncer needs to be run to initialize the account. as the user who will run vdirsyncer later on run this command:
-  VDIRSYNCER_CONFIG=/opt/owncloud/vdirsyncer/bin/photokiste.conf /opt/owncloud/vdirsyncer/bin/vdirsyncer sync
+  VDIRSYNCER_CONFIG=/opt/owncloud/photokiste.conf /opt/owncloud/vdirsyncer/bin/vdirsyncer discover photokiste
+now vdirsyncer can be run through cron or manually like this:
+  VDIRSYNCER_CONFIG=/opt/owncloud/photokiste.conf /opt/owncloud/vdirsyncer/bin/vdirsyncer sync
 that's it :) .. theoretically vdirsyncer should also support two way sync, but i haven't tried that..  however they seem confident in their solution so it might be worth a try even for two-way syncing :)
+==== Update Vdirsyncer ====
+you can run updates using pipsi as well:
+  pipsi --home /opt/owncloud/ upgrade
+==== fix vdirsyncer after OS upgrade ====
+you might just need to re-install vdirsyncer after a os upgrade because the python version behind the virtualenv changed and is no longer compatible with the environment. in that case just rename the ''/opt/owncloud/vdirsyncer'' directory and start from scratch as listed above. Make sure you keep your configs!