56881b92d0
In the past Google Calendar exports were done by first removing all events of a day and then create new ones. This takes a lot of time for export and runs into Google Calendar usage limits after some time. By now content will be compared before removing/creating a single event one. To be able to do so, all other sync sources and targets have been removed, so its only possible to export from database to Google Calendar by this change. To trigger an export you need to create a trigger file. run_jobs.pl runs periodically e.g. started by cron and checks if a trigger file exists and start sync_cms.pl to export the selected events to the Google Calendar. Trigger files and jobs are configured at jobs.config. Each job has a source and target file containing the access data for calcms and the calendar. Configuration files have been cleaned up. Old Accounts and passwords have been removed. They hopefully should have been not active for a long time ;-)
19 lines
478 B
Plaintext
19 lines
478 B
Plaintext
<config>
|
|
|
|
start_dir /home/calcms/agenda/admin/jobs/start/
|
|
log_dir /home/calcms/agenda/admin/jobs/logs/
|
|
|
|
<job>
|
|
title potsdam : sender berlin -> 88vier.de
|
|
name potsdam_to_88vier.de
|
|
command /home/radio/calcms/sync_cms/sync_jobs/calcms_to_google.sh -7 31 potsdam
|
|
</job>
|
|
|
|
<job>
|
|
title frb : sender berlin -> 88vier.de
|
|
name frb_to_88vier.de
|
|
command /home/radio/calcms/sync_cms/sync_jobs/calcms_to_google.sh -7 31 frb
|
|
</job>
|
|
|
|
</config>
|