Closed joefiorini closed 11 years ago
Hmm. It sounds like some have had success manually patching nack. Can you try throwing gem 'json', '1.7.7'
in your ~/.labrador/Gemfile
as a quick workaround?
I had to actually manually update the Gemfile.lock since labrador does deployment bundles by default. I got working by making Labrador use json 1.8.0.
On Fri, Aug 2, 2013 at 11:16 AM, Chris McCord notifications@github.comwrote:
Hmm. It sounds like some have had success manually patching nack. Can you try throwing gem 'json', '1.7.7' in your ~/.labrador/Gemfile as a quick workaround?
— Reply to this email directly or view it on GitHubhttps://github.com/chrismccord/labrador/issues/25#issuecomment-22012459 .
This happened after running your install script and then going to labrador for a given app. Might be related to 37signals/pow#378? Thoughts?