Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Its a well known best practice to use run executables using bundle exec <command> and not just the command. But it seems like nobody could explain why its better to run executebles via bundle exec. So I ask yo why,…?
If you are using bundle exec instead of just executing command, bundler makes some changes to your environment variable, so all gems listed in your Gemfile can be accessed successfully. You can see http://gembundler.com/man/bundle-exec.1.html . Also, bundler can install gems into custom path instead of system location and then they still will be accessible for require if you are using
bundle exec. See also http://gembundler.com/man/bundle-install.1.htmlSo in general answer is: to isolate your set of gems from system gems and to make them available for you application in case of custom gem location.