Differences

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

--- owncloud [21.03.2017 06:41] – [synchronize external caldav and carddav sources] Pascal Suter
+++ owncloud [11.02.2019 09:52] – [synchronize external caldav and carddav sources] Pascal Suter
@@ Line 156: / Line 156: @@
 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!