freeipa/install
2011-08-18 23:24:29 -04:00
..
conf Add option to install without the automatic redirect to the Web UI. 2011-08-18 23:24:29 -04:00
html Fixed browser configuration pages 2011-08-17 17:28:25 +00:00
migration Fixed broken links in ipa_error.css and ipa_migration.css. 2011-08-11 13:38:36 +00:00
po ticket 1650 - compute accurate translation statistics 2011-08-18 14:25:58 +02:00
share Fixed browser configuration pages 2011-08-17 17:28:25 +00:00
tools Add option to install without the automatic redirect to the Web UI. 2011-08-18 23:24:29 -04:00
ui Replaced page dirty dialog title. 2011-08-19 16:43:09 +00:00
updates Correct sudo runasuser and runasgroup attributes in schema 2011-07-19 08:06:41 -04:00
configure.ac ticket 1650 - compute accurate translation statistics 2011-08-18 14:25:58 +02: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.