I would guess the commands you're issuing don't match the stack your on.

All you should need is the credentials and the app name for the gem, but saying 
this I've only done this on Cedar so YMMV.

Neil


On 16 Nov 2011, at 14:09, Corey Trager wrote:

> Not working yet.
> 
> Testing on my dev box, heroku.restart resulted in a 404 but
> heroku.ps_restart DID restart my app running at Heroku, so that was
> promising.  That is, my local app A could restart my Heroku app B.
> But, when deployed to Heroku and tried to have B restart itself,
> ps_restart resulted in "NoMethodError" for Heroku::Client and restart
> resulted in RestClient::ResourceNotFound.
> The NoMethodError, does that mean I'm using an older stack with an
> older Heroku gem?
> The RestClient, I guess heroku needs to know a host?   So, I'm looking
> for docs for the gem.
> Do you think I'm on the right track?
> 
> 
> On Nov 15, 5:04 pm, Neil Middleton <[email protected]> wrote:
>> You can always use the Heroku gem to talk to the heroku infrastructure as 
>> the CLI does.
>> 
>> For instance:
>> 
>> @heroku = Heroku::Client.new(ENV["HEROKU_EMAIL"], ENV["HEROKU_PASSWORD"])
>> 
>> You can then issue commands such as:
>> 
>> @heroku.restart('app_name')
>> 
>> Neil
>> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Heroku" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to 
> [email protected].
> For more options, visit this group at 
> http://groups.google.com/group/heroku?hl=en.
> 

-- 
You received this message because you are subscribed to the Google Groups 
"Heroku" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/heroku?hl=en.

Reply via email to