Nope - it's pretty simple.  There's no "migration" per se -- just create a new 
app on cedar  "heroku create --stack cedar"  and push your app there instead.

Start with that and let us know if there's any change in the output. 

-- 
Jon McCartie


On Tuesday, April 17, 2012 at 8:40 AM, Senna wrote:

> Hi Jon,
> 
> I tried adding the sass_heroku initializer but still have the same
> issue. Is migrating the app to cedar complicated?
> 
> On Apr 17, 8:30 am, Jon McCartie <[email protected] (http://gmail.com)> 
> wrote:
> > I've never done a Rails 3.1+ app on bamboo.  Have you tried deploying this 
> > to a cedar app?
> > 
> > Here's a good read for this error as 
> > well:http://stackoverflow.com/questions/7713151/rails-3-1-active-admin-her...
> > 
> > --
> > Jon McCartie
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > On Tuesday, April 17, 2012 at 7:27 AM, Senna wrote:
> > > This is really annoying. It works fine locally (development) but when
> > > I push it to Heroku it crashes on the first HTTP request, then if I
> > > press F5 it works fine. So it seems to crash when the app first spins
> > > up. ANY advise would be greatly appreciated! I'm on bamboo-mri-1.9.2
> > > 
> > 
> > 
> > > I think this is where the error is in the Heroku Log output:
> > 
> > > 2012-04-14T20:09:19+00:00 app[web.1 (http://web.1)]: Sass::SyntaxError 
> > > (File to
> > > import not found or unreadable: bourbon.
> > > ...
> > > 2012-04-14T19:08:14+00:00 app[web.1 (http://web.1)]: 
> > > .bundle/gems/ruby/1.9.1/gems/
> > > railties-3.2.3/lib/rails/railtie/configurable.rb:30:in
> > > `method_missing'
> > > 
> > 
> > 
> > > Complete Heroku Log Output:http://pastebin.com/raw.php?i=rvdkPwzR
> > 
> > > --
> > > SD Ruby mailing list
> > > [email protected] (mailto:[email protected])
> > > http://groups.google.com/group/sdruby
> > > 
> > 
> > 
> 
> 
> -- 
> SD Ruby mailing list
> [email protected] (mailto:[email protected])
> http://groups.google.com/group/sdruby
> 
> 


-- 
SD Ruby mailing list
[email protected]
http://groups.google.com/group/sdruby

Reply via email to