3 ms·
I think this is more of a problem with ruby gems then 3rd party libraries in general. Maintaining gems across dev/test/prod environments is probably more compli
by ericwaller 18y ago
I think this is more of a problem with ruby gems then 3rd party libraries in general. Maintaining gems across dev/test/prod environments is probably more complicated than just packaging 3rd party source with your app.
It's certainly possible to package gems with the app, but I don't know of any established best practice for it.
- catch23 18y agoIf you're on rails, it's rake rails:freeze:gems. If you're using Merb, you can use frozen-merb. If you're just using some adhoc ruby script, you can always install your necessary gems in your home directory in .gems or something and symlink that whenever you need it.