nicholas a. evans

I've been meaning to add an alternate config syntax, with the current config syntax as a shorthand notation. It's never really come up as an issue for me though. I'd...

To deal with your issue though, you ought to be able to make and use your own very simple config loader, that can easily workaround the character limit: https://github.com/nevans/resque-pool#custom-configuration-loader

In particular, I'd like to analyze the most significant or longest lived forks and see if there's anything we need to merge from them that might impact backwards compatibility. If...

The most important of these branches (custom config loader) was merged and released in `0.6.0.rc1`. Please help test it (and the other changes) out, if you can.

go ahead and send a pull request for ERB support. It should be simple enough to hack in.

shouldn't be hard at all. see Heroku's blog post: [Logs are Streams, Not Files](http://adam.heroku.com/past/2011/4/1/logs_are_streams_not_files/)

Not intentional. It was meant to fix a problem with running `resque-pool` inside docker. I think that you should be able to temporarily workaround this by telling the Gemfile to...

That looks like an invalid config to me. It ought to be a {"queue spec" => count} hash, and nil count indicates an error. We could silently eat the nil...

It's a good idea! I personally use don't use resque-scheduler. I just use cron jobs (using `busybox` cron!) that do no more than e.g. "`script/resque_enqueue CronJobs::Hourly`", etc. But there are...

I might get around to this before the end of the year, but... I probably won't. 😉 I _am_ going to migrate my biggest `resque-pool` deployment from simple cron jobs...