Can not Resque.new

[ponny]

I'm having a huge amount of trouble getting Resque to work. I must be missing something very big because I'm following the steps from your README. I'm using Rails 4:

2.0.0dev > Resque::VERSION
=> "1.24.1"
2.0.0dev > Resque.new
NoMethodError: undefined method `new' for Resque:Module

Same issue with master:
gem 'resque', :git => 'git://github.com/resque/resque.git'

This would not work:
gem "resque", "> 2.0.0.pre.1"
Because:
Could not find gem 'resque (> 2.0.0.pre.1) ruby' in the gems available on this machine.

[steveklabnik]

You missed this line:

Also, this README is written first, so lots of things in here may not work the exact way that they say they might here. Yay 2.0!

;)

I'll leave this open because it hasn't been implemented yet.

[steveklabnik]

If you're using 1.24.1 (and you should be) you should be reading the 1.x readme: https://github.com/resque/resque/blob/1-x-stable/README.markdown

[ponny]

Resque.new didn't work for v2 either. V2 not ready to use yet?

2.0.0dev :001 > Resque::VERSION
=> "2.0.0.pre.1"
2.0.0dev :002 > Resque.new
NoMethodError: undefined method `new' for Resque:Module

As a quick sidenote, is there a way to tell resque not to run a job for say 30 minutes?

[steveklabnik]

Yes, V2 is nowhere near done yet. We're working on reafactorings, getting code under test, the site, documentation, and figuring out the right interface for 2.0 yet.

not to run a job for say 30 minutes?

You'll want to use resque-scheduler.

[jacobo]

I noticed that "what we want it to be" example is very close to the abandoned rails 4 Q API
Is this this the goal?

If so, are you interested in seeing something like this as a PR to resque:
rails/rails#9924

If not, what other ideas do we have for a "better" API? Where is this discussion happening and how can I be involved?

[steveklabnik]

I want @jeremy in on this discussion, as the Rails 4 queue API was specifically rejected. I'd prefer Resque to be it near-directly.
—
Sent from Mailbox for iPhone

On Mon, May 13, 2013 at 6:58 PM, Jacob Burkhart notifications@github.com
wrote:

I noticed that "what we want it to be" example is very close to the abandoned rails 4 Q API
Is this this the goal?
If so, are you interested in seeing something like this as a PR to resque:
rails/rails#9924

If not, what other ideas do we have for a "better" API? Where is this discussion happening and how can I be involved?

Reply to this email directly or view it on GitHub:
#976 (comment)

[cdrage]

As per 4b04fb8

and http://words.steveklabnik.com/rescuing-resque-again

"We will plan on making this switch in the next couple of weeks. If you feel this is the wrong move, please let us know. But since active development will in fact happen on 1.x, this feels like the correct thing."

Let's close these issues? #1175

[steveklabnik]

Yes, this is a good point, thanks!