Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Note about Resque.redis config #469

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Note about Resque.redis config #469

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
View file
Open in desktop
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
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