Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
/__better_errors does not work if there was no error #54
Hi, first of all: GREAT WORK MAN!!!
when i request the page /__better_errors it shows the generic error page instead better_errors one. if i force an error the page works as it should.
thanks for this great work!
Yes, you need an exception for a REPL. A shell is ran in the context of an error's backtrace. I don't think @charliesome has plans for a standalone REPL yet.
You can't have a REPL in production. By design, the
Same answer as 2.
I urge you to reconsider finding a solution to getting a REPL shell in a production environment... that seems like a bad idea. Instead, I suggest integrating it into your deploy process: there are ways to integrate a
An in-browser REPL console (independent of an associated error) seems like a cool idea though.
added a commit
Dec 14, 2012
This comment has been minimized.
This comment has been minimized.Show comment Hide comment
Being able to instantly access your app's console (without having to boot up the entire Rails stack) does actually sound like a compelling feature. (Especially if better_errors starts coming up with pretty ways of representing Ruby objects in HTML.)
I think this is another feature that should be optional.