freeipa/install
2011-04-22 15:22:31 -04:00
..
conf rename static to ui 2011-01-20 14:12:47 +00:00
html error handling style 2011-01-25 16:47:09 -05:00
migration Use ldapi: instead of unsecured ldap: in ipa core tools. 2011-03-03 14:04:34 -05:00
po Fix some minor issues uncovered by pylint. 2011-04-20 14:38:02 -04:00
share Wait for memberof task and DS to start before proceeding in installation. 2011-04-22 11:43:50 +02:00
tools Fix some minor issues uncovered by pylint. 2011-04-20 14:38:02 -04:00
ui make use of new user-find columns. 2011-04-22 15:22:31 -04:00
updates The default groups we create should have ipaUniqueId set 2011-04-15 13:02:17 +02:00
configure.ac rename static to ui 2011-01-20 14:12:47 +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.