Cool. I'd really like to use pry for my production console. Is there a way to start a Rails Pry console in production without forcing my coworkers to do the same?
A slight twist on 'Pry in Production' I've done is to drop a call to `binding.pry` in the code on a staging server. Then I can step through production data and inspect what's going on.
If you use pry in production on heroku you don't need to do anything special like have a separate machine. Since every time you run it, Heroku spins up a new dyno, it has zero effect on the rest of your running platform.
Thanks for providing the service. We use it at Acquia for Ruby, PHP and Javascript and are really happy with the product.
We've discovered quite a few small edge cases and hickups in our apps. They happen rarely and mostly with older accounts / random network timeouts / ... and while they don't really bother users, they are still fun to fix :)
Thanks, I'll give it a try, though I'm using Minitest. I haven't really tried much yet on that front; I mostly just got to the point of realizing that this issue I'm working on now is really going to be a pain to get figured out without a debugger.
For this project, I just switched, like a month or so ago, to an all-Vim workflow. I mostly feel more productive in it so far, but a real debugger is the one thing that I had been putting off figuring out.
I built a small testing framework with a pry workflow as one of it's goals. It's possible to run the tests in pry mode which drops you into a pry session on test failure. I've used it on several small libs & the test+pry workflow is quite nice. https://github.com/hopsoft/micro_test
15 comments
[ 4.5 ms ] story [ 46.0 ms ] threadA slight twist on 'Pry in Production' I've done is to drop a call to `binding.pry` in the code on a staging server. Then I can step through production data and inspect what's going on.
https://github.com/rweng/pry-rails/blob/master/Readme.md
Thanks for providing the service. We use it at Acquia for Ruby, PHP and Javascript and are really happy with the product. We've discovered quite a few small edge cases and hickups in our apps. They happen rarely and mostly with older accounts / random network timeouts / ... and while they don't really bother users, they are still fun to fix :)
For this project, I just switched, like a month or so ago, to an all-Vim workflow. I mostly feel more productive in it so far, but a real debugger is the one thing that I had been putting off figuring out.