owncloud

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revisionBoth sides next revision
owncloud [27.03.2016 17:04] Pascal Suterowncloud [27.03.2016 18:34] Pascal Suter
Line 128: Line 128:
   export CPLUS_INCLUDE_PATH=/usr/include/libxslt/:/usr/include/libxml2/   export CPLUS_INCLUDE_PATH=/usr/include/libxslt/:/usr/include/libxml2/
   /opt/owncloud/vdirsyncer/bin/pip install vdirsyncer   /opt/owncloud/vdirsyncer/bin/pip install vdirsyncer
 +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
 +b = photokiste_owncloud
 +collections = null
 +conflict_resolution = a wins
 +
 +[storage photokiste_crm]
 +type = http
 +url = https://www.source-server.com/ical.ics
 +
 +[storage photokiste_owncloud]
 +type = caldav
 +url = https://my.owncloud.server/remote.php/dav/calendars/username/calenarname
 +username = myuser
 +password = mysecret
 +</code>
 +the owncloud calendar name can be viewed by hovering over the calendar. it will appear as mouse pointer tooltip. 
 +
 +one thing on the ical format.. i used a library called ''PHP iCalWriter'' which i generated the ical source file with. as it turns out, PHP iCalWriter writes an different DTSTART and DTEND field for whole-day-events than what owncloud accepts. i have no idea who's write and who's wrong, but since i PHP iCalWriter is open source and it is already quite an old version i am using i decided to simply modify it. make sure, that your ical file contians a DTSTART and DTEND that look like this for whole-day-events (that is, events where the start and end date does not contain a time): 
 +  DTSTART;VALUE=DATE:20160903
 +and a line like this for date + time start and end dates: 
 +  DTSTART:19701025T030000
 +(PHP iCalWriter never added the ;VALUE=DATE: portion). 
 +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: 
 +  VDIRSYNCER_CONFIG=/opt/owncloud/vdirsyncer/bin/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 :)
  
  • owncloud.txt
  • Last modified: 16.07.2021 00:30
  • by Pascal Suter