whenever/README.rdoc

140 lines
5.3 KiB
Plaintext
Raw Permalink Normal View History

2009-02-17 00:47:21 +00:00
== Introduction
2009-02-16 03:24:10 +00:00
Whenever is a Ruby gem that provides a clear syntax for writing and deploying cron jobs.
2009-06-24 20:37:37 +00:00
2009-02-16 03:24:10 +00:00
== Installation
$ gem install whenever
2009-02-17 01:08:15 +00:00
Or with Bundler in your Gemfile.
gem 'whenever', :require => false
2009-02-16 03:24:10 +00:00
== Getting started
2009-02-17 00:47:21 +00:00
$ cd /my/rails/app
$ wheneverize .
2009-02-16 03:24:10 +00:00
This will create an initial "config/schedule.rb" file you.
== Example schedule.rb file
2009-02-26 22:25:56 +00:00
2009-02-18 18:29:20 +00:00
every 3.hours do
runner "MyModel.some_process"
rake "my:rake:task"
command "/usr/bin/my_great_command"
2009-02-16 03:24:10 +00:00
end
2009-02-18 18:29:20 +00:00
every 1.day, :at => '4:30 am' do
2009-02-26 22:25:56 +00:00
runner "MyModel.task_to_run_at_four_thirty_in_the_morning"
2009-02-16 03:24:10 +00:00
end
every :hour do # Many shortcuts available: :hour, :day, :month, :year, :reboot
2009-02-17 01:08:15 +00:00
runner "SomeModel.ladeeda"
2009-02-16 03:24:10 +00:00
end
every :sunday, :at => '12pm' do # Use any day of the week or :weekend, :weekday
2009-02-16 03:24:10 +00:00
runner "Task.do_something_great"
end
2009-02-18 18:29:20 +00:00
More examples on the wiki: http://wiki.github.com/javan/whenever/instructions-and-examples
== Define your own job types
Whenever ships with three pre-defined job types: command, runner, and rake. You can define your own with `job_type`.
For example:
job_type :awesome, '/usr/local/bin/awesome :task :fun_level'
every 2.hours do
awesome "party", :fun_level => "extreme"
end
Would run `/usr/local/bin/awesome party extreme` every two hours. `:task` is always replaced with the first argument, and any additional `:whatevers` are replaced with the options passed in or by variables that have been defined with `set`.
The default job types that ship with Whenever are defined like so:
job_type :command, ":task :output"
job_type :rake, "cd :path && RAILS_ENV=:environment rake :task :output"
job_type :runner, "cd :path && script/runner -e :environment ':task' :output"
If a script/rails file is detected (like in a Rails 3 app), runner will be defined to fit:
job_type :runner, "cd :path && script/rails runner -e :environment ':task' :output"
If a `:path` is not set it will default to the directory in which `whenever` was executed. `:environment` will default to 'production'. `:output` will be replaced with your output redirection settings which you can read more about here: http://github.com/javan/whenever/wiki/Output-redirection-(logging-your-cron-jobs)
All jobs are by default run with `bash -l -c 'command...'`. Among other things, this allows your cron jobs to play nice with RVM by loading the entire environment instead of cron's somewhat limited environment. Read more: http://blog.scoutapp.com/articles/2010/09/07/rvm-and-cron-in-production
You can change this by setting your own job_template.
set :job_template, "bash -l -c ':job'"
Or set the job_template to nil to have your jobs execute normally.
set :job_template, nil
And you'll see your schedule.rb converted to cron sytax. Note: running `whenever` with no options does not display your current crontab file, it simply shows you the output of converting your schedule.rb file.
2009-02-16 03:24:10 +00:00
== Capistrano integration
2010-10-18 22:51:27 +00:00
Use the built-in Capistrano recipe for easy crontab updates with deploys.
2009-02-16 03:24:10 +00:00
2010-10-18 22:51:27 +00:00
In your "config/deploy.rb" file:
2009-02-17 00:47:21 +00:00
2010-10-18 22:51:27 +00:00
require "whenever/capistrano"
2010-10-18 22:51:27 +00:00
Take a look at the recipe for options you can set. http://github.com/javan/whenever/blob/master/lib/whenever/capistrano.rb
For example, if you're using bundler do this:
2010-10-18 22:51:27 +00:00
set :whenever_command, "bundle exec whenever"
require "whenever/capistrano"
== The `whenever` command
$ cd /my/rails/app
$ whenever
This will simply show you your schedule.rb file converted to cron syntax. It does not read or write your crontab file. Run `whenever --help` for a complete list of options.
2009-02-19 01:09:31 +00:00
== Credit
2009-02-26 22:25:56 +00:00
Whenever was created for use at Inkling (http://inklingmarkets.com) where I work. Their take on it: http://blog.inklingmarkets.com/2009/02/whenever-easy-way-to-do-cron-jobs-from.html
2009-02-17 19:38:37 +00:00
2009-02-19 01:10:14 +00:00
While building Whenever, I learned a lot by digging through the source code of Capistrano - http://github.com/jamis/capistrano
2009-02-19 01:09:31 +00:00
2009-06-24 20:37:37 +00:00
== Discussion / Feedback / Issues / Bugs
For general discussion and questions, please use the google group: http://groups.google.com/group/whenever-gem
2009-02-16 03:24:10 +00:00
2009-06-24 20:37:37 +00:00
If you've found a genuine bug or issue, please use the Issues section on github: http://github.com/javan/whenever/issues
Ryan Bates created a great Railscast about Whenever: http://railscasts.com/episodes/164-cron-in-ruby
It's a little bit dated now, but remains a good introduction.
== License
2010-04-26 16:09:40 +00:00
Copyright (c) 2009+ Javan Makhmali
Permission is hereby granted, free of charge, to any person
obtaining a copy of this software and associated documentation
files (the "Software"), to deal in the Software without
restriction, including without limitation the rights to use,
copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the
Software is furnished to do so, subject to the following
conditions:
The above copyright notice and this permission notice shall be
included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
OTHER DEALINGS IN THE SOFTWARE.