I'm able to run the application and open it in browser. Not sure if I have made a mistake while configuring.
Rubymine debugger code#
So instead, we simply overwrite the relevant code inside the bundle with something that works for our case for now.Īs soon as the PR is merged and released, we can revert to installing the official, unaltered version into our docker container.Īs soon as the PR is merged and released, we can revert to installing the official, unaltered version into our docker have tried to use your branch, but still, I'm getting below error message.
Rubymine debugger install#
The combination of these three aspects renders it impossible to easily install a version that includes the fix. * We cannot use the monkey-patch in an initializer as proposed in the issue, because wagon:test doesn't run Rails and thus doesn't consider the initializers * The fix with SO_REUSEPORT is only available on a specific branch of a specific fork, which is not up-to-date with the prerelease version * The newest RubyMine requires a prerelease version of ruby-debug-ide So we need to use `gem install` in the Dockerfile to do it * We cannot easily modify the Gemfile because it is not in the same repository. This hack is necessary as long as ruby-debug/ruby-debug-ide#164 is not merged and released because: Note : The find_free_port method is moved in the 0.7 beta of Ruby Debug IDE to lib/ruby-debug-ide/ruby-debug-ide.rb.Įdit (Dec 11/18): Added check that the Debugger::MultiProcess is defined.Īs similarly proposed in ruby-debug/ruby-debug-ide#107 There was no issues when running the application using Unicorn without debugging (i.e. I decided to use Unicorn in development to be consistent with production and when I did the switch I ran into the above issue when debugging. Part of the application is multi-threaded which would hang the Thin webserver since it's single threaded by default. I'm supporting an older application that previously used Thin as it's development webserver but Unicorn in production. In development I only use one process so I just hard coded the port but you could setup a range if you wanted too. Web_1 | Fast Debugger (ruby-debug-ide 0.6.1, ruby-debug-base19x 0.11.30.pre15, file filtering is not supported) listens on 0.0.0.0:58438 Web_1 | => Rails 3.2.16 application starting in development on Other info, I'm not using "Docker for Mac" I installed docker tools via brew and and my default docker machine is using the parallels driver.įast Debugger (ruby-debug-ide 0.6.1, ruby-debug-base19x 0.11.30.pre15, file filtering is not supported) listens on 0.0.0.0:1234
Rubymine debugger how to#
Do you have any suggestions on how to get around this? I'm having trouble finding documentation on the sub-debugger. Rdebug-ide -d -host 0.0.0.0 -port 1234 -dispatcher-port 26162 - /usr/local/bundle/bin/rails s -b 0.0.0.0 -p 3000 -e developmentįast Debugger (ruby-debug-ide 0.6.1.beta4, debase 0.2.2.beta9, file filtering is supported) listens on 0.0.0.0:1234ĥ: Processing in control: b /myapp/app/api/v1/users.rb:6įast Debugger (ruby-debug-ide 0.6.1.beta4, debase 0.2.2.beta9, file filtering is supported) listens on 0.0.0.0:37922ĥ: Ide process dispatcher notified about sub-debugger which listens on 37922