Sha256: 6d55b6c3d0310e0aa852d156bb49e4acd360758c72c1c99f3a150b93fba4fe65
Contents?: true
Size: 1.38 KB
Versions: 20
Compression:
Stored size: 1.38 KB
Contents
h1. Development Here is information for developers. h2. Repository ActiveLdap uses ["git repository on GitHub":https://github.com/activeldap]. Here is a list to get each source code. - "activeldap":https://github.com/activeldap/activeldap := <pre class="command"> % git clone https://github.com/activeldap/activeldap.git </pre> =: - "al-admin":https://github.com/activeldap/al-admin := <pre class="command"> % git clone https://github.com/activeldap/al-admin.git </pre> =: h2. Issues ActiveLdap uses "Issues on GitHub":https://github.com/activeldap/activeldap/issues for issue tracking. Please submit a issue when you find an issue. h2. Rails 3 support Here is design about Rails 3 support. h3. must * We add active_ldap/test_help.rb to support ActiveLdap fixture. We don't write same codes into test_helper.rb like http://ruby-activeldap.rubyforge.org/activeldap-fabrication/en/#Install h3. may * We support Warden. * We support Devise * We support OmniAuth. (instead of Warden) h3. DONE * We don't support Rails 3.0.x. * We provide active_ldap/railtie to initialize ActiveLdap. * We remove ActiveRecord dependency. * We depend on ActiveModel instead of ActiveRecord. * We target to Rails 3.1.0. (Yes, it's not released yet but it will be released before we support Rails 3.x.) * We update the documentation and ensure that the procedure for including ActiveLdap in a Rails 3 project is correct.
Version data entries
20 entries across 20 versions & 2 rubygems