4 ms·

Title is somewhat false, since you still rely on rubygems for deployment. It's just that you cache bundled gems and don't have to hit rubygems unless really nee

• steveklabnik 14y ago
  > Title is somewhat false, since you still rely on rubygems for deployment. Under normal circumstances, you do not hit Rubygems.org at all. If your cache is out of date, bundler will automatically hit Rubygems.org for you, but you can also update the cache from your locally installed gems, and then it won't. Which means no, you do not hit Rubygems.org while deploying. If you can deploy while Rubygems.org is down, that's 'not relying on Rubygems.org' in my book. > Also noteworthy: described bundler usage is the default behavior of capistrano bundler recipe. Thank you for confirming. I haven't used cap in a few years, and I thought so, but I didn't check yet.