ChiliProject is not maintained anymore. Please be advised that there will be no more updates.
We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.
User shouldn't use bundle (Feature #936)
Description
Installation guide on wiki contains a step Install the required gems using bundler.
I think 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.
History
Updated by John Yani at 2012-03-18 12:09 am
Here is an exact quote:
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.
Updated by Felix Schäfer at 2012-03-23 11:06 am
I think it's a stretch to call people installing ChiliProject "end-users" as in most cases you'll also have to setup at least a web server and a DB, maybe some repositories too.
I agree that having some "wizard" to take you through the bundle install step would be nice though, a rake task maybe?
Updated by Felix Schäfer at 2012-03-23 02:57 pm
Updated by John Yani at 2012-03-24 09:08 pm
Felix Schäfer wrote:
I agree that having some "wizard" to take you through the bundle install step would be nice though, a rake task maybe?
Yes, rake task would be great.
Speaking of which, see #522. Would you agree that this issue is a duplicate or at least would be solved by #522?
Oh, I should've look for it. Yes, it's a duplicate.
I've also posted it in redmine: http://www.redmine.org/issues/10475 http://www.redmine.org/issues/10474
BTW, wouldn't it be great to add a field "Redmine issue # (if exist)"? It would increase interoperability between two projects.
Updated by Felix Schäfer at 2012-03-25 07:12 am
John Yani wrote:
Oh, I should've look for it. Yes, it's a duplicate.
OK, closing here then.
I've also posted it in redmine: http://www.redmine.org/issues/10475 http://www.redmine.org/issues/10474
BTW, wouldn't it be great to add a field "Redmine issue # (if exist)"? It would increase interoperability between two projects.
That's what the "Remote issue URL" is for :-)
- Status changed from Open to Duplicate