1 hour ago · 10 min read2056 words · Tech · hide · 0 comments

geneva_drive is the first thing I’ve put out for money on my own, without an org behind my back - and a rollercoaster on many fronts. One of the less obvious ones is the actual distribution: how does geneva_drive get to your servers or dev machines, once you have that ticket? It works via paquette - my little engine for serving libraries. Here’s how it got made, and why. I am currently available for contract work. Hire meto help make your Rails app better! The idea is simple: you purchase access to some distribution point for a commercial package, you point your package manager to it, and your package management system (bundler or npm or what have you) does the rest. This is pretty much how it was done by the pioneers in the scene - namely sidekiq and Avo. When I tried to figure out how it actually worked under the hood, though, it turned out to be simpler than what I needed. Most of those are just copies of an existing codebase for distributing gems - either geminabox or gemcutter…

No comments yet. Log in to reply on the Fediverse. Comments will appear here.