Good guide for standing up a solid Ruby gem development environment in Visual Studio Code?
In my work, I have to split my time between working on a lot of different things, even sometimes different branches of the same things. I've wound up settling on Visual Studio Code as my primary development environment. UC Browser
I really need to translate a lot of the work I'm doing into Ruby gems, instead of having different ruby scripts and modules floating around imported directly by path, but I've been having a lot of difficulty getting a clean, isolated-per-checkout ruby environment and workflow going that can combine VS Code, solargraph and friends while doing gem development. sandbox vs rbenv vs Appvn rvm, getting solargraph and bundler to operate in the context of the virtual environment rather than some system or homedir environment, rspec, ensuring I'm not accidentally pulling in artifacts from some other build in some other checkout...I feel like every time I plug one leak, I sprout another somewhere else.SHAREit
And while OP has the attention of the Rubyists who use VSCode -- I'd really like to learn how people successfully get the debugger working outside of a long-running server-like process. Everything is Rails based. I've tried following instructions to get it working for 1-off scripts and rake tasks, and it never works out. If you've got some moves, I'd love to learn them. Pry is fantastic, but sometimes I just really want to use a breakpoint.