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.
Remove the ldap and openid groups in the Gemfile (Feature #1042)
Description
Those gems are pure ruby and don't hurt anyone. I think it would be save to always require them to further cleanup the mess of our many bundler groups.
Thoughts?
Associated revisions
Better error message and AR errors in log for failed LDAP on-the-fly user creation (closes #932, #1042).
git-svn-id: http://redmine.rubyforge.org/svn/trunk@1345 e93f8b46-1217-0410-a6f0-8f06a7374b81
History
Updated by Holger Just at 2012-06-15 09:33 pm
Hmmm, this could be misunderstood. I want to put the gems into the outer scope to always require them, effectively removing the "choice" of whether the gems should be installed or not.
Updated by Felix Schäfer at 2012-06-16 04:58 pm
I don't mind having them in the global "gem" scope, though I'd se it as a goal to have things like alternate authentication backends (LDAP, OpenID) as plugins down the line.
Updated by Holger Just at 2012-06-16 05:56 pm
If we manage to move to something like devise, the actual gems are only downstream-requirements of the authentication plugins. In the end, user can add those plugins at will (with some plumbing).
Updated by Felix Schäfer at 2012-06-18 12:46 pm
Holger Just wrote:
If we manage to move to something like devise, the actual gems are only downstream-requirements of the authentication plugins. In the end, user can add those plugins at will (with some plumbing).
Sure, we just have to keep it in mind :-)