Skip to content

Commit

Permalink
README example of description inside a Google Event
Browse files Browse the repository at this point in the history
  • Loading branch information
Fabrice Bernhard committed Jan 15, 2012
1 parent 5341ec5 commit 796644d
Showing 1 changed file with 10 additions and 1 deletion.
11 changes: 10 additions & 1 deletion README.md
Expand Up @@ -26,7 +26,7 @@ See http://www.pfspear.net/projects/gcalcron for his first version.
* GCal<->Cron syncs can be run at any given frequency, depending on your desired reactivity
* Does not rely on permanent Internet connectivity thanks to the 7-days-ahead scheduling
* Only the new and modified events are downloaded from Google at each run, for minimal bandwidth and latency
* Timezone/DST aware (relies on time.altzone)
* Timezone/DST aware, using datetutil.tz.gettz (new since 2012-01-16)
* Simple settings file in JSON format
* No Google password stored
* DocTests! :-)
Expand Down Expand Up @@ -80,7 +80,16 @@ For example, to sync every 10 minutes, run `crontab -e`, and add the following l

* In your Google Calendar, create a single or recurrent event, and list one command per line in the description.
* Add `+10: ` or `-5: ` at the beginning of the line to add an offset of `+10` minutes or `-5` minutes to the command
* Add `end: ` or `end -5: ` at the beginning of the line to add an offset relative to the end of the event
* Example:

```bash
-60: /usr/bin/python /home/automation/heating_on.py
-10: /usr/bin/python /home/automation/boiler_on.py
-2: /usr/bin/python /home/automation/boiler_off.py
/usr/bin/php /root/phpdenon/wakeup.php
end: /usr/bin/python /home/automation/heating_off.py
```

## Development

Expand Down

0 comments on commit 796644d

Please sign in to comment.