Using pry in production
bugsnag.com
Using pry in production
1–10 of 16 posts
Re: Using pry in production
#2Cool. 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.
Re: Using pry in production
#3Cool. 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.
Installing the pry gem doesn't stop anyone from using irb if they prefer.
Re: Using pry in production
#4If 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.
Re: Using pry in production
#5If 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.
Until you start making ActiveRecord calls...
Re: Using pry in production
#6Unrelated to pry, related to bugsnag:
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 :)
Re: Using pry in production
#7Cool. 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.
Installing the pry gem doesn't stop anyone from using irb if they prefer.
The way the article does it (using pry rails) will make 'rails console' use pry, so it does affect my coworkers.
Re: Using pry in production
#8That's pretty cool. What I'd really like to know, though, is if anybody knows how to drop into a pry-debugger debug session during a unit test.
Re: Using pry in production
#9Earlier quoted context omitted.
Installing the pry gem doesn't stop anyone from using irb if they prefer.
The way the article does it (using pry rails) will make 'rails console' use pry, so it does affect my coworkers. https://github.com/rweng/pry-rails/blob/master/Readme.md
Ah, got it. I misunderstood your question.
Re: Using pry in production
#10Cool. 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.
> $ RAILS_ENV=production bin/pry -r ./config/environment