CODEWITHSUNDEEP
rubybundler
ScottJ
ScottJ

Reputation: 1092

Bundler: ensure production gems installed system-wide?

I have a ruby program in my git repo, used by a team. It's executed directly out of the git repo. I don't want all the team members to have to deal with gems, so I want the production-level gems to be installed system-wide (on shared disk). Bundler will use the git-controlled Gemfile.lock to decide which gems to pick up.

For development, I often install gems using --user-install.

Problem: I might accidentally push changes that use gems which are only user-installed, which will break other team members when they pull and try to run.

How can I ensure that all non-development gems are installed system-wide?

Is there a bundle command I can run that will detect this and throw an error? Or can I somehow get my cucumber tests to run using only system gems?

Upvotes: 0

Views: 356

Answers (1)

Ginty
Ginty

Reputation: 3501

There is no way to get Bundler to use System gems, though I think there should be: https://github.com/bundler/bundler/issues/1964

The most straightforward solution for you would be to package the gems into your Git repo: http://bundler.io/v1.12/bundle_package.html. This is really how the bundler team recommend that it should be run in a case where you want a user to be able to run your app without having to install gems locally.

A second option would be for you to use the --path option to bundle install and point that to a shared location visible to all your users. This option is remembered, so check .bundle into your Git repo and then your users would use the same configuration and reference the same location when they run bundle. Since all of the gems would already be installed there by you, they would have no problems.

Upvotes: 3

Related Questions