freeipa/install
amitkuma e6ca3b0c73 Removing extra spaces present in man ipa-server-install
There are extras space present in man page. PR removes
identified extra spaces.

Reviewed-By: Stanislav Laznicka <slaznick@redhat.com>
2018-03-06 10:11:52 +01:00
..
certmonger Have all the scripts run in python 3 by default 2018-02-15 18:43:12 +01:00
html Address more 'to login' 2017-12-12 12:53:21 +01:00
migration logging: do not log into the root logger 2017-07-14 15:55:59 +02:00
oddjob Have all the scripts run in python 3 by default 2018-02-15 18:43:12 +01:00
restart_scripts Have all the scripts run in python 3 by default 2018-02-15 18:43:12 +01:00
share Convert ipa-pki-proxy.conf to use mod_ssl directives 2018-02-21 07:57:40 +01:00
tools Removing extra spaces present in man ipa-server-install 2018-03-06 10:11:52 +01:00
ui webui: hbactest: add tooltips to 'enabled' and 'disabled' checkboxes 2018-02-22 16:27:11 -03:00
updates ACI: grant access to admins group instead of admin user 2018-02-19 15:51:44 +01:00
wsgi logging: do not log into the root logger 2017-07-14 15:55:59 +02:00
Makefile.am Move HTTPD cert/key pair to /var/lib/ipa/certs 2018-02-21 07:57:40 +01: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.