freeipa/install
Endi Sukma Dewata 6bd2f5ba35 Fixed host managed-by adder dialog.
The host managed-by adder dialog has been fixed to use the new
--not-man-hosts option to filter out hosts that are already added.

Ticket #1675
2012-01-31 08:40:00 -06:00
..
conf Configure s4u2proxy during installation. 2012-01-10 22:39:26 -05:00
html Fixed inconsistent image names. 2011-10-27 14:05:12 +00:00
migration ticket 2022 - modify codebase to utilize IPALogManager, obsoletes logging 2011-11-23 09:36:18 +01:00
po update i18n pot file for branch master 2012-01-03 16:36:34 -05:00
share Configure s4u2proxy during installation. 2012-01-10 22:39:26 -05:00
tools Check for the existence of a replication agreement before deleting it. 2012-01-30 17:27:55 +01:00
ui Fixed host managed-by adder dialog. 2012-01-31 08:40:00 -06:00
updates Use correct template variable for hosts, FQDN. 2012-01-17 17:51:12 +01:00
configure.ac Fixed inconsistent image names. 2011-10-27 14:05:12 +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.