Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -147,6 +147,17 @@ default `'text'`)
* `VERBOSE` - Maximize log verbosity if non-empty (equivalent to a level
of `MonoLogger::DEBUG`, default `false`)

*Warning: If you use a different redis database, other than the default database (0), to store your redis jobs, you will have store the Resque.redis into the initializer file*
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This isn't necessarily true, though. I think it would be clearer to say that specifying the full Redis URL within the schedule process is important and perhaps give some examples of how to do this, just like in the resque web example. I would also support adding the Redis URL as an env/cli option so that initializers are not necessary.


```
resque-scheduler [other options] --initializer-path script/resque-scheduler.init.rb
```

```ruby
# script/resque-scheduler.init.rb
require 'resque'
Resque.redis = Redis.connect url: 'redis://localhost:6379/X'.freeze # Where X is the selected redis database number
```

### Resque Pool integration

Expand Down