freeipa/install
2012-02-29 12:59:13 +01:00
..
conf Implement password based session login 2012-02-27 05:57:43 -05:00
html Fixed inconsistent image names. 2011-10-27 14:05:12 +00:00
migration ticket 2022 - modify codebase to utilize IPALogManager, obsoletes logging 2011-11-23 09:36:18 +01:00
po update translation pot file 2012-02-21 17:19:20 -05:00
share Tweak the session auth to reflect developer consensus. 2012-02-27 05:54:29 -05:00
tools Fix bad merge of not calling memberof task when re-initializing a replica 2012-02-27 20:23:10 -05:00
ui Static metadata update - new DNS options 2012-02-29 12:59:13 +01:00
updates Global DNS options 2012-02-24 09:40:40 +01:00
configure.ac Fixed inconsistent image names. 2011-10-27 14:05:12 +00:00
Makefile.am rename static to ui 2011-01-20 14:12:47 +00:00
README.schema Add some basic rules for adding new schema 2010-08-27 13:40:37 -04:00

Ground rules on adding new schema

Brand new schema, particularly when written specifically for IPA, should be
added in share/*.ldif. Any new files need to be explicitly loaded in
ipaserver/install/dsinstance.py. These simply get copied directly into
the new instance schema directory.

Existing schema (e.g. in an LDAP draft) may either be added as a separate
ldif in share or as an update in the updates directory. The advantage of
adding the schema as an update is if 389-ds ever adds the schema then the
installation won't fail due to existing schema failing to load during
bootstrap.

If the new schema requires a new container then this should be added
to install/bootstrap-template.ldif.