freeipa/install
Simo Sorce 6bbd4eed9f Rename add command to connect in ipa-replica-manage
This change also improves command syntax parsing

Fixes: https://fedorahosted.org/freeipa/ticket/623
2010-12-21 17:28:13 -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 Change FreeIPA license to GPLv3+ 2010-12-20 17:19:53 -05:00
po Change FreeIPA license to GPLv3+ 2010-12-20 17:19:53 -05:00
share Remove common entries when deleting a master. 2010-12-21 17:28:13 -05:00
static populate the group select upon initial creation 2010-12-21 13:37:23 -05:00
tools Rename add command to connect in ipa-replica-manage 2010-12-21 17:28:13 -05:00
updates Move automount, default HBAC services, netgroup and hostgroup bootstrapping. 2010-12-17 17:31:19 -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.