Note about Resque.redis config

[danlo]

In regards to #468. I missed that resque-scheduler was completely stand-alone and wouldn't catch on to that I use a different redis database other than the default 0 for resque jobs.

I've added this warning in the hopes that other people who also use a different redis database like will avoid this problem.

[juanibiapina]

Does it run standalone even if a dependency to "environment" is specified? In that case it should pick up Redis config from an initializer, right?

The weirdest thing for me is that schedules actually work, but delayed jobs don't. I think.

[meatballhat]

@juanibiapina Sorry for delay! I don't think your question can be answered without knowing the specifics of how your code is loaded. The flexibility of this part of the configuration is a constant source of question bugs, unfortunately 🙍

[juanibiapina]

My problem was another issue. Scheduler wasn't able to elect a master node properly. I cleaned up redis and it worked.

[carsonreinke]

@danlo Is this still relevant? It seems like simply stating that configuration comes from Resque.redis would be sufficient.