3 ms·
Good point! I suspect the issue will be running tests. From what I gather they did all this to save developers the pain of compiling ruby gems + specific stuff
by blueplanet200 5y ago
Good point! I suspect the issue will be running tests. From what I gather they did all this to save developers the pain of compiling ruby gems + specific stuff on your environment (which can be a huge pain...)
If you edit a file using some sync over ssh option, and want to run a test - how do you proceed? And how is this not the same thing as just checking out the git repo locally in the first place?
- mastax 5y ago> If you edit a file using some sync over ssh option, and want to run a test - how do you proceed? Well you have your files synced over ssh and also have a terminal over ssh which you use to run your tests. Am I missing something? > And how is this not the same thing as just checking out the git repo locally in the first place? It's not just avoiding cloning the git repo. It's avoiding building all the dependencies and getting them configured and running. For most of my projects that's not a big deal but I expect GitHub has several databases with specific configuration, memcached or redis, maybe custom patched builds, etc.
- blueplanet200 5y agoYeah fair, if you run the tests in the cloud that saves you a step (filesystem sync via ssh is still in effect the same as a git clone I'd argue...) If you check out code in RubyMine, it'll try and install the dependencies in the Gemfile regardless, though.