31–40 of 50 posts
I'm a complete rails newbie. I've added 'better_errors' into my Gemfile, started my server/also with Pow and yet I see the same errors as before?
then start the server again: rails server
Bugsnag (http://bugsnag.com) is awesome when debugging production errors.
You guys would be amazed if you tried frameworks like Symfony (instead of discarding PHP for not being beautiful or whatever). It has always had these features, and in Symfony2 it only got more awesome. You even have a complete analysis for each request, that you can open with one click: https://s3.amazonaws.com/i.imm.io/OvjX.jpeg https://s3.amazonaws.com/i.imm.io/Ovk9.jpeg Edit: Being downvoted. Some people just don…
You guys would be amazed if you tried frameworks like Symfony (instead of discarding PHP for not being beautiful or whatever). It has always had these features, and in Symfony2 it only got more awesome. You even have a complete analysis for each request, that you can open with one click: https://s3.amazonaws.com/i.imm.io/OvjX.jpeg https://s3.amazonaws.com/i.imm.io/Ovk9.jpeg Edit: Being downvoted. Some people just don…
I came to Rails from Symfony and there are definitely things I miss. Rails is way better overall, but there are loads of little things that were fantastically useful.
I'm a complete rails newbie. I've added 'better_errors' into my Gemfile, started my server/also with Pow and yet I see the same errors as before?
go to the root project in the shell, stop rails server if it's running and type: bundle install then start the server again: rails server
As with nearly all Rack application servers I know of, you can simply restart the application by creating/updating 'tmp/restart.txt' from your Rails root. Unix's `touch` command does this nicely. With Pow specifically, you can also create '~/.pow/restart.txt' (or '~/Library/Application Support/Pow/Hosts/restart.txt', since it's the same location) and that will force Pow to reload itself.
An inline REPL? I love you more than I have words, particularly if you can somehow snag context for it.
Earlier quoted context omitted.
go to the root project in the shell, stop rails server if it's running and type: bundle install then start the server again: rails server
If he is running under Pow, there's no reason to be running 'script/server' or 'rails server'. That's what Pow does for you. As with nearly all Rack application servers I know of, you can simply restart the application by creating/updating 'tmp/restart.txt' from your Rails root. Unix's `touch` command does this nicely. With Pow specifically, you can also create '~/.pow/restart.txt' (or '~/Library/Application Support/…
Also, I've tried that and I'm still getting the same old "Action Controller: Exception..." error. Specifically I have a MySQL error, yet no 'better_errors' showing.
I've already executed 'bundle install' too.
To get it to work with my mixed Padrino/Sinatra rack app I had to do this in each app:
if PADRINO_ENV == "development"
set :raise_errors, true
set :show_exceptions, false
end
use BetterErrors::Middleware if PADRINO_ENV == "development"
I'm not deeply familiar with Padrino or Sinatra and so it took a lot of experimentation (and source reading) to find the right incantation. But it's working great now!
You guys would be amazed if you tried frameworks like Symfony (instead of discarding PHP for not being beautiful or whatever). It has always had these features, and in Symfony2 it only got more awesome. You even have a complete analysis for each request, that you can open with one click: https://s3.amazonaws.com/i.imm.io/OvjX.jpeg https://s3.amazonaws.com/i.imm.io/Ovk9.jpeg Edit: Being downvoted. Some people just don…
No offense, but there is no way in hell I would look at that page for hours on end coding, it looks like it was designed in 3 minutes.