freeipa/install
Adam Young 67d1c07112 kinit typo
Was origially KInit  but the command is kinit
2010-12-17 16:36:48 -05:00
..
conf SUDO Rule Search and Details Pages 2010-11-19 16:53:30 -05:00
html type prevented rendering on firefox4 2010-12-17 16:07:09 -05:00
migration Rewrite the migration page using WSGI 2010-11-09 13:25:17 -05:00
po managed entry hostgroup netgroup support https://fedorahosted.org/freeipa/ticket/543 2010-12-13 17:56:12 -05:00
share Use nsContainer and not extensibleObject for masters entries 2010-12-15 10:58:03 -05:00
static kinit typo 2010-12-17 16:36:48 -05:00
tools Add krb5-pkinit-openssl as a Requires on ipa-server package 2010-12-16 09:33:11 -05:00
updates Re-implement access control using an updated model. 2010-12-01 20:42:31 -05:00
configure.ac build tweaks - use automake's foreign mode, avoid creating empty files to satisfy gnu mode - run autoreconf -f to ensure that everything matches 2010-11-29 11:39:55 -05: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.