freeipa/install
Stanislav Levin e89493e260 Add title to 'add' dialog for 'Topology' entity
To improve translation quality the title of 'Add' dialog should be
specified explicitly in the spec and should be an entire sentence.

Fixes: https://pagure.io/freeipa/issue/7707
Reviewed-By: Serhii Tsymbaliuk <stsymbal@redhat.com>
2018-10-01 10:28:14 +02:00
..
certmonger Generate scripts from templates 2018-08-23 14:49:06 +02:00
html Fix javascript 'errors' found by jslint 2018-09-27 16:33:25 +02:00
migration Fix javascript 'errors' found by jslint 2018-09-27 16:33:25 +02:00
oddjob Generate scripts from templates 2018-08-23 14:49:06 +02:00
restart_scripts Generate scripts from templates 2018-08-23 14:49:06 +02:00
share Disable authentication to endpoint for serving i18n requests 2018-07-17 15:32:28 -04:00
tools Py3: Remove subclassing from object 2018-09-27 11:49:04 +02:00
ui Add title to 'add' dialog for 'Topology' entity 2018-10-01 10:28:14 +02:00
updates Support Samba 4.9 2018-09-26 11:40:19 +02:00
wsgi Add absolute_import future imports 2018-04-20 09:43:37 +02:00
Makefile.am Encrypt httpd key stored on disk 2018-03-23 12:48:46 +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.