(RubyMine) Check when you cannot debug with docker-compose

reference Tutorial: Docker Compose as a remote interpreter — RubyMine

I tried to do it according to the reference page and did the same, but for some reason it didn't work and I would like to summarize it easily, including myself in the future.

When it doesn't work,

--Settings / Preferences Dialog> Languages ​​& Frameworks | Remote to use with Ruby SDK and Gem Check if'debase' and'ruby-debug-ide' are included ――If it doesn't work, erase what you have already made above and make it again <= I solved this.

--Settings / Preferences dialog> Languages ​​& Frameworks | When adding a new remote with the Ruby SDK and Gem, make sure the service has the service name specified in docker-compose.yml

--Check if a different container is running --Try to delete the .idea directory, docker container, image, network, volume and start from the beginning --Check if Rails> Development: project name in the execution / debug configuration. No need to create Docker> docker-compose with + button

If you can do this, the ▷ button or the bug button will launch the app, making it easier to start development. (You don't have to type a command)

Recommended Posts

(RubyMine) Check when you cannot debug with docker-compose
Precautions when creating PostgreSQL with docker-compose
Check when moss with SimpleDateFormat parse
You can't (yet) pass arguments to buildkit with docker-compose
A memo to check when you try to use Lombok