3 ms·
This. People seem terrified of running their own gem or apt repositories to mirror their dependencies - or even to host their own code. The dirty little secre
by regularfry 13y ago
This. People seem terrified of running their own gem or apt repositories to mirror their dependencies - or even to host their own code.
The dirty little secret is that these things are trivial to set up. Anyone whose build or deploy has been broken by github, rubygems.org, ruby-lang.org or even rvm.io falling over is Doing It Wrong. While I empathise, I have very little sympathy for people panicking when github gets DDoSed again.
- mpvh 13y agorelated - I've used this for running my own Gem server for years - It really is trivial: https://github.com/geminabox/geminabox https://github.com/geminabox/geminabox
- regularfry 13y agoIt can be even simpler. I use Apache serving static files out of /var/www/gems, and a cron job to rebuild the index every 5 minutes if anything's changed. Caching gems is just `rsync -avz $GEM_HOME/cache <server>:/var/www/gems/`. Publishing internal gems I've built is just scp.
- angelbob 13y agoGeminabox is simple until you want to run with a lot (500+) of gems. And then index-building is horrible - it basically never finishes. The complexity comes in mirroring the right set of other people's gems, which match the exact combined set of all versions used in all your various projects. There is not a good "pass-through" gem server that just automatically mirrors what it is asked for from RubyGems. There really, really should be.