forked from prebeta/DemereLaunchPage
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathRakefile
44 lines (34 loc) · 1.46 KB
/
Rakefile
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
# Add your own tasks in files placed in lib/tasks ending in .rake,
# for example lib/tasks/capistrano.rake, and they will automatically be available to Rake.
require File.expand_path('../config/application', __FILE__)
Rails.application.load_tasks
# require 'rufus/scheduler'
# require 'resque/tasks'
# require 'resque/scheduler/tasks'
# task 'resque:setup' => :environment
# task "resque:setup" => :environment do
# ENV['QUEUE'] = '*'
# end
# namespace :resque do
# task :setup do
# require 'resque'
# # you probably already have this somewhere
# Resque.redis = 'localhost:6379'
# end
# task :setup_schedule => :setup do
# require 'resque-scheduler'
# # If you want to be able to dynamically change the schedule,
# # uncomment this line. A dynamic schedule can be updated via the
# # Resque::Scheduler.set_schedule (and remove_schedule) methods.
# # When dynamic is set to true, the scheduler process looks for
# # schedule changes and applies them on the fly.
# # Note: This feature is only available in >=2.0.0.
# # Resque::Scheduler.dynamic = true
# # If your schedule already has +queue+ set for each job, you don't
# # need to require your jobs. This can be an advantage since it's
# # less code that resque-scheduler needs to know about. But in a small
# # project, it's usually easier to just include you job classes here.
# # So, something like this:
# end
# task :scheduler => :setup_schedule
# end