Wiki suggests to install the required gems using bundler. By default bundler install all the groups. I thought that opt-in option would be better, so I've submitted an issue on GitHub https://github.com/carlhuda/bundler/issues/1771
The issue was closed with rationale that an end-user shouldn't use bundler, and it is a completely developer tool. So they've suggested that user should call bundle using rake task and strongly discourage using bundler by end-users directly.
If you are planning on shipping your application to true end-users, I strongly suggest that you do not ask them to run bundle install at all.
Instead, package your application so they can simply download it and then run it.
You may want to investigate the new bundle install --standalone option that is part of Bundler 1.1, which was designed to assist with that exact problem.
So I'm asking, could redmine make installation as simple as running ./install_redmine script?
Updated by Jean-Philippe Lang about 11 years ago
- Tracker changed from Defect to Feature
- Subject changed from Users shouldn't use bundle to Installation script
I agree that it would be nice to configure which gems are installed by default but bundler makes it really easier to install the dependencies, and for end users as well.
The installation script would be nice but installing the gems is just a first step. What would this script be supposed to do? Install required gems, create the database, configure apache/passenger virtualhost... ?
Updated by John Yani about 11 years ago
Redmine can be prepackaged with all required gems and user won't have to use bundle at all.
This issue is related to #10474
This script could run bundler in all plugins directories independently with "--path ../../vendor/bundle"