Our great sponsors
gemstash | Bundler | |
---|---|---|
1 | 4 | |
739 | 4,822 | |
0.3% | - | |
8.4 | 7.6 | |
3 months ago | about 4 years ago | |
Ruby | Ruby | |
MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
gemstash
Posts with mentions or reviews of gemstash.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-03-24.
-
MimeMagic versions prior to 0.3.6 have been yanked from RubyGems and it's GPL 2.0 now
Sorry to hear. I'd say, never "bundle install" in the init script. If using docker, make "bundle install" an intermediate container. If you have your own servers, try network FS sharing your deps (and see if you're ok with the "require" latencies). Alternatively, use a gem cache proxy. You can use "geminabox" with a rubygems mirror, if you can tolerate the space and long mirroring times, or use a purposed "middleman" proxy, like gemstash, or nexus if your company is multilang.
Bundler
Posts with mentions or reviews of Bundler.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-03-22.
-
current state of bundle install vs gem install -g
bundle install uses the bundle binary (technically a ruby script). The command runs the Bundler::Installer.run module. There are a lot more steps, particularly around dependencies. It ultimately calls Bundler::Installer::GemInstaller.
-
My tone doesn’t make me wrong, or how I convinced the Ruby project to fix an inconsistency
sudo is totally unacceptable on my system
-
RubyGems has the most legal problems. Explanation?
On the license in 2011: Bundler, which most people use to generate gem scaffolding, added the MIT license as default in 2011. I bet you'll see a change around that time where older gems are more likely to have a different license (Apache 2.0 maybe?) and newer gems are more often MIT. I'd also guess older gems are more likely to be indirect dependencies since they're probably (?) more likely to implement lower level pieces which were since wrapped up, so this could explain that phenomenon too.
-
Caching All Native Ruby Gem Platforms
If you are using Bundler version 1.x, you may also need to set the specific_platform configuration setting.
What are some alternatives?
When comparing gemstash and Bundler you can also consider the following projects:
Gem in a Box - Really simple rubygem hosting
RubyGems - The Ruby community's gem hosting service.
gemdiff - Find source repositories for ruby gems. Open, compare, and update outdated gem versions