Root Path: /home/patmetheny (The root path on the server) Create Deployment Configuration Tools → Deployment → ConfigurationĬlick the + to add a server and give it a name of your choice
The following steps were completed in RubyMine 8.0.4. On to the good stuff! Configuring RubyMine for Remote Debugging via Vagrant Hopefully these steps help you out if you find yourself in a similar situation. The following are the steps I took to get remote debugging working successfully on a project that used Vagrant and Packer. My first stab at getting the remote debugger working was wrought with confusion, frustration, and, well, there would have been some hair pulling if I had any. I've seen quite a few different Ruby on Rails projects, and every single one of them has had significantly different server configurations. Perhaps a strong contributor to part of the under-utilization, even for those who have already chosen to use RubyMine, is the fact that remote debugging can be tricky to set up and get working correctly. I consider RubyMine a good IDE, and based on my experience with Ruby on Rails teams, I can't help but feel like RubyMine and its debugger is an under-utilized jewel. But I mostly used Eclipse and IntelliJ during much of my formative programming years, and I rather enjoy a good IDE.
True enough, there are really good gems like Pry that provide debugging functionality. This is especially true when working with Ruby and Rails.įor me, one downside to using Vim, though, is that I really enjoy being able to use the debuggers that are part and parcel of IDEs. This is certainly understandable, because each of those editors provides so many ways to extend functionality and allows developers to be extremely productive in whichever way suits them best. I mostly work with developers who prefer Vim or Emacs as their editor of choice.
0 kommentar(er)
