My .pryrc for debugging and productivity

[justin]

Here are a few more tips:

1. I mostly use Pry rather than RubyMine because it’s way faster to get to the debugger. You can modify the Rails app without restarting.
2. You must not run the Rails command within the context of foreman. If you’re using foreman to start Rails and other processes, you will need to either comment out the Rails process or run foreman like this: foreman start -f Procfile.dev -m webpack-client-bundle=1,webpack-server-bundle=1 where webpack-client-bundle and webpack-server-bundle are your processes to start.
3. If you run puma by default, you might want to switch the application server for debugging so that you don’t have multiple threads going at once. Running rails s might do the trick.

Be sure to also see:

Favorite Rails and JavaScript debugging tips

Rails debugging. Starting with the debugger is often WAY to slow. Way faster to put in print statements, but sometimes you want to poke around. Here’s a cool hack: Add an intentional syntax error, and get the better_errors console to poke around! WAY faster than debugger! And check out pry. See my Pry tips here: