freeipa/install
2010-10-28 07:58:31 -04:00
..
conf IPA HTTPD config uses /usr/share/static as target for /ipa/ui 2010-08-09 15:07:06 -04:00
html Get merged tree into an installalble state. 2009-02-03 15:29:20 -05:00
migration Add DS migration plugin and password migration page. 2010-01-20 16:54:17 -05:00
po Update Ukrainian (uk.po) translation 2010-10-19 14:14:23 -04:00
share UUIDs: remove uuid python plugin and let DS always autogenerate 2010-10-28 07:58:31 -04:00
static Field Errors Uses the pattern field of the metat data to see if the input for a given field is valid. If not, displays a red box with the contents of pattern_msg 2010-10-28 03:06:28 -04:00
tools Include REPLICA_FILE in usage for ipa-replica-install 2010-10-13 13:01:05 -04:00
updates UUIDs: remove uuid python plugin and let DS always autogenerate 2010-10-28 07:58:31 -04:00
configure.ac Changes to the install and config files to support deploying the javascript code. 2010-08-06 11:55:52 -04:00
Makefile.am Changes to the install and config files to support deploying the javascript code. 2010-08-06 11:55:52 -04: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.