The file-based synchronization mode keeps one or more local calendar file(s) in sync with your Google Calendar and vice versa.
After installing this program, your Evolution calendar should be able to subscribe and modify a remote Google Calendar.
1) Install GCALDaemon (Java 1.5 required).
mkdir -p /usr/local/sbin
chgrp -R usergroup /usr/local/sbin/GCALDaemon
chmod -R g+w /usr/local/sbin/GCALDaemon
chmod 755 /usr/local/sbin/GCALDaemon/bin/*.sh
2) Launch Evolution, and click the 'New Calendar' menu on the Calendars page.
3) Create a new local calendar, maybe named 'Google Calendar'.
4) Quit Evolution, and see which calendar file has been added to
the 'user home/.evolution/calendar/local' folder by the Evolution.
The calendar file's path would look like the following:
5) Open the 'gcal-daemon.cfg' configuration file.
6) Put the full path to 'calendar.ics'
for the variable 'file.ical.path'.
# Full path of the local iCalendar file
7) Encode your Gmail password with the 'password-encoder.sh'.
Input your password and press ENTER. Copy the encoded password.
8) Put your Gmail address for the variable 'file.google.username'.
# Gmail user (your full email address)
9) Put your encoded password for the variable 'file.google.password'.
# Gmail password (use password encoder!)
10) Copy the iCal URL for your calendar's Private Address on the Calendar Settings page.
11) Put your iCal URL for the variable 'file.private.ical.url', without protocol and hostname.
# URL (without hostname) of the Google Calendar's private ical file
12) Set the 'file.enabled' property to 'true'.
# Enable iCalendar file listener/synchronizer
13) Start GCALDaemon ('standalone-start.sh' or 'sync-now.sh').
INFO | GCALDaemon V1.0 beta 16 starting...
INFO | Local time zone is Pacific Standard Time.
INFO | HTTP server disabled.
INFO | RSS/ATOM feed converter disabled.
INFO | Start listening file /home/me/.evolution/calendar/*/calendar.ics...
INFO | File listener started successfully.
INFO | LDAP server disabled.
INFO | Gmail notifier disabled.
INFO | Sendmail service disabled.
14) Restart Evolution.
Items added (or modified/deleted) to your Evolution calendar will now automatically appear in your Google Calendar.
15) Evolution loads 'calendar.ics' at startup.
Then it caches this file after it is first compiled and does not poll
for file changes until you restart the application. As a result, if GCALDaemon make changes
in 'calendar.ics', you must restart Evolution before those changes take effect.
To avoid data loss, do not modify your Google Calendar with Evolution and with Web-browser simultaneously.
The 'file.offline.enabled' option is the only one difference between the
offline (dial-up) and online (fast) Google Calendar synchronization.
To enable GCALDaemon's offline synchronization algorithm,
follow the step-by-step instructions about the
Desktop configuration (Permanent Internet connection),
then set the 'file.offline.enabled' property to 'true'.
# Turn it on when you use dial-up connection (default is "false")
Permanently connected (always online) mode:
GCALDaemon downloads your Google Calendar's iCalendar file every 10 minutes
(see the 'file.polling.google' property). In the meantime
GCALDaemon's file scanner listens the changes in the local iCalendar files,
and updates the remote Google Calendar events almost immediately,
using small portion of XML messages
(see the 'file.polling.file' property).
This mode is much more faster than the offline algorithm,
but does not support offline working.
Dial-up (offline-enabled) mode:
GCALDaemon compares your Google Calendar (if available) and local iCalendar file every 10 minutes,
and does all modifications together.
If it is unable to do so because the network is unavailable, it tries again when it detects network presence.
The average network usage of these (online / offline) modes are equal.
This mode is particularly useful for NoteBook users and for third-party phone/PDA synchronizers.
This feature is a variant of the offline/dial-up mode.
When you launch the 'GCALDaemon/bin/sync-now.sh' script,
GCALDaemon synchronize your calendar files, then stop.
You can create a shortcut icon on your desktop for the script,
or you can invoke it at user login automatically.
To set up multiple file listeners, you need to configure
a path-username-password-url set for each of the Google Calendars you want to synchronize (the first listener definition is
unindexed, the others are indexed from '2'):
# First calendar
# Second calendar
# Third calendar
File-based synchronizer can convert RSS/ATOM XML files to iCalendar format,
therefore you can read news, blogs and tweets with Evolution Calendar.
This feature makes copying feed entries to Google Calendar a simple copy/paste operation.
Once the entry copied to the Google Calendar, you can edit it as an average calendar event.
Another advantage is that you can add directly To Do (Task) items to the converted calendar.
Note: feed converter must be enabled (feed.enabled=true).
# Google Calendar
# BBC Technology RSS News (without username/password)
# Twitter ATOM feed (with username/password)
1) If there is no need for HTTP-based synchronization, set the
'http.enabled' property to 'false' (in 'gcal-daemon.cfg').
We recommend to set this for the lower memory usage and for the higher security.
The authentication and the ATOM-based communication between Google and
GCALDaemon is secure (SSL) and cannot be intercepted by a third party.
2) Put a 'work.dir' property into 'conf/gcal-daemon.cfg'
to specify the work directory of GCALDaemon.
This directory is the 'GCALDaemon/work' folder by default.
For people that use multiple operating systems it is handy that the work
directory is another directory.
Also, it's more secure if the work files wouldn't reside in the program
directory but on eg. an encrypted partition.
Note: After you set up a new directory,
you may copy the old work folder's content
into the new one.
# GCALDaemon's work directory
1) Default synchronization:
iCal alarm property synchronized unidirectionally (move property from iCal to Google Calendar).
Google Calendar supports discrete alarm values only (5-10-15-20-25-30-45 mins, 1-2-3 hours,
1-2 days, or one week). GCALDaemon converts different values into such an values
(e.g. 17 min to 15 min, 6 day to one week, etc).
Category, priority and URL properties are unsupported by the Google Calendar API.
|iCalendar event property
||Google Calendar event property
|all day event (true / false)
||all day event (true / false)
|status (tentative / confirmed / canceled)
||status (tentative / confirmed / canceled)
|classification (public / private)
||visibility (public / private)
|transparency (transparent / opaque)
||transparency (transparent / opaque)
|list of attendees
||list of participants
|recurrence rule (including exceptions)
||recurrence rule (including exceptions)
||one-way only (iCal to Google)
2) Extended synchronization:
GCALDaemon is able to synchronize on these four iCalendar property in 'extended mode':
alarm (two-way), category, priority and URL.
This is useful if you'd like to sync Google Calendar with your PDA (in dial-up or sync-on-demand mode).
To enable this feature set the 'extended.sync.enabled' property to 'true'.
Note: Needless use of the extended mode (especially with large calendars) can significantly reduce the performance.
# Enable to sync alarms, categories, urls and priorities
|iCalendar event property
||Google Calendar event property
|category (Business, Birthday, etc)
|priority (low, medium, high)
3) Google Calendar - unlike Evolution - does not support To Do (Task) items.
Therefore GCALDaemon stores To Do items in a local file storage.
This storage is the 'GCALDaemon/work' folder.
Before uninstall an older GCALDaemon version, you should archive this directory.
If the new GCALDaemon installation finishes, you can restore
the previous 'work' folder, including the old To Do items.
About the 'online' synchronization: to avoid data loss, do not modify
your local calendar files when GCALDaemon is not running properly (or stopped)
and the 'file.offline.enabled' property is 'false'.
Note: GCALDaemon automatically creates daily backups of each and every local
and remote calendar into the 'work/backup' subdirectory,
so your files are always safe and secure.