Move group authorization strategies into separate classes
authorMarius Mathiesen <marius@gitorious.org>
Tue, 10 Jul 2012 13:47:46 +0000 (15:47 +0200)
committerMarius Mathiesen <marius@gitorious.org>
Mon, 8 Oct 2012 07:41:32 +0000 (09:41 +0200)
commitafa2ee539a93ce636ab4d13a1622b2b28765a069
tree1f234624a9b084d9f8caea1ac64a33fb35f2973e
parent1d99479116381178fa36b1a11f698905d6f8d36f
Move group authorization strategies into separate classes

Our include/extend/configure setup has reached a level where I'm unable to
make an elegant solution at 4pm on a Tuesday.

Construct separate classes (strategies?) for Group and Ldap group authorization
backends to reduce code clutter.
lib/gitorious/authorization/database_authorization.rb
lib/gitorious/authorization/group_authorization.rb [new file with mode: 0644]
lib/gitorious/authorization/ldap_group_authorization.rb [new file with mode: 0644]