Ruby on Rails Saturday, May 27, 2017

Is your controller class name named properly and have you committed this controller to version control before deploying to Herkoku?

Sent from my iPhone

On May 27, 2017, at 8:15 AM, Joe Guerra <JGuerra@jginfosys.com> wrote:

Hi, I'm not sure why my app on heroku is crashing.  
I've added a requests controller, and everything works locally using sqlite.  


here's my log from heroku...

2017-05-27T13:07:36.250694+00:00 app[web.1]:    [1m [35mUser Load (1.7ms) [0m  SELECT  "users".* FROM "users" WHERE "users"."id" = $1  ORDER BY "users"."id" ASC LIMIT 1  [["id", 11]]
2017-05-27T13:07:36.253544+00:00 app[web.1]: Completed 500 Internal Server Error in 8ms (ActiveRecord: 1.7ms)
2017-05-27T13:07:36.254583+00:00 app[web.1]: 
2017-05-27T13:07:36.254585+00:00 app[web.1]: NameError (uninitialized constant RequestsController::Request):
2017-05-27T13:07:36.254586+00:00 app[web.1]:   app/controllers/requests_controller.rb:12:in `index'
2017-05-27T13:07:36.254586+00:00 app[web.1]: 

What's causing this?  any suggestions?
Thanks,
Joe

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/75f23d83-3b51-4e4c-b408-0b1d8e8f0cb2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment