When running #Rails apps, I've started just running each of the commands in Procfile.dev in separate terminal tabs (rails s, yarn) plus Siqekiq. It lets me use binding.break (or equivalent) and have it be useable.

@collin If you're on Rails 7, or using `ruby/debug`, you can use remote debugging while running all the processes using the Procfile

https://binarysolo.chapter24.blog/remote-debugging-in-rails-7/

Remote debugging in Rails 7 | Binary Solo

This post was extracted and adapted from The Rails and Hotwire Codex. Rails 7 includes the official Ruby debugger. It also uses Foreman to orchestrate multiple processes in development. This way you can run the Rails server along with processes to watch and compile your frontend assets using a single command. Annoyingly, this makes debugging trickier. You can't just add a breakpoint in your app and run commands in the console. The same Terminal window is running multiple processes, so won't...

Binary Solo
@ayush I'll have to read that! I really like my editor, but it doesn't have a graphical debugger. I never figured out how to make this work any other way.
@ayush so doing it this way lets you connect interactively, so you can use bin/dev, but you're still putting breakpoints in your code?

@collin Yep exactly ... you'd need to use a terminal though, I don't know how to make it work within an editor ...

I'm sure there must be a way but I don't like fiddling with text editors, prefer to just use the command line

@collin I use #overmind, which uses tmux underneath, to run everything. Then, I can connect to a given process using overmind connect web to get to the debugger.

https://github.com/DarthSim/overmind

GitHub - DarthSim/overmind: Process manager for Procfile-based applications and tmux

Process manager for Procfile-based applications and tmux - DarthSim/overmind

GitHub