freeipa/install
Pavel Vomacka 0b8d460191 WebUI: fix jslint error
jslint warned about parsing string to integer without explicit radix.
This error was introduced in commit 3cac851 .

Reviewed-By: Alexander Bokovoy <abokovoy@redhat.com>
2017-07-24 14:20:36 +02:00
..
certmonger renew agent: get rid of virtual profiles 2017-05-15 12:14:28 +02:00
conf Changing cert-find to go through the proxy instead of using the port 8080 2017-06-16 08:56:53 +02:00
html fix spelling mistake; minor rewording 2017-05-19 09:52:46 +02:00
migration logging: do not log into the root logger 2017-07-14 15:55:59 +02:00
oddjob wsgi, oddjob: remove needless uses of Env 2017-07-14 15:55:59 +02:00
restart_scripts Turn off OCSP check 2017-06-06 13:33:54 +02:00
share logging: do not reference loggers in arguments and attributes 2017-07-14 15:55:59 +02:00
tools logging: do not log into the root logger 2017-07-14 15:55:59 +02:00
ui WebUI: fix jslint error 2017-07-24 14:20:36 +02:00
updates Create indexes for 'serverhostname' attribute 2017-07-04 14:40:52 +02:00
wsgi logging: do not log into the root logger 2017-07-14 15:55:59 +02:00
Makefile.am Configure HTTPD to work via Gss-Proxy 2017-02-15 07:13:37 +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.