On Dec 18, 9:14 am, Ralph Shnelvar <[email protected]> wrote: > Because my ISP is giving me zero help in fixing a problem I fee is his > problem, I have decided to migrate my code to Heroku. > > I attempted a port but the port failed. Oh well, it was worth a try. > > So, instead, I did "Hello, world" by doing > rails new ultradedup001 > > I actually saw the "Welcome aboard" screen > athttp://ultradedup001.heroku.com/(Yay!) > > When I then clicked on "About your application’s environment", I see > "The page you were looking for doesn't exist." in what appears to be a > frame. I suspect this is generated in javascript. >
The /rails/info route is only setup in development, so if your heroku deployment is running in production it's normal for it not to work. Fred > When I do a > heroku logs > the relevant lines seem to be > > 2011-12-18T08:54:59+00:00 app[web.1]: Started GET > "/rails/info/properties" for 67.172.135.123 at 2011-12-18 00:54:59 -0800 > > 2011-12-18T08:54:59+00:00 heroku[router]: GET > ultradedup001.heroku.com/rails/info/properties dyno=web.1 queue=0 > wait=0ms service=482ms status=404 bytes=728 > > 2011-12-18T08:54:59+00:00 app[web.1]: ActionController::RoutingError (No > route matches "/rails/info/properties"): > > Any thoughts on what I did wrong? Or is the "Welcome aboard" code not > portable to Heroku? > > -- > Posted viahttp://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en.
