rubocop-daemon
rubocop-daemon copied to clipboard
Add a option to expose daemon's TCP port
The gem's idea is great, but it can't be used from remote environments (for example, from docker), because it can't expose TCP port.
This pull-request is to add a option for exposing TCP port to external. I suppose that, rubocop-daemon run as docker container and user use rubocop-daemon-wrapper on host machine.
The option name, --binding
, is from same feature of rails new
.
But I'm not particular about the option name, so it's ok to rename it.
FIY, the usecase's article is here (Japanese only): https://zenn.dev/cumet04/articles/fast-rubocop-on-docker
I tested it and it perfectly working!