freeipa/install
Pavel Vomacka be7865bf4f Change activity text while loading metadata
After log in into webui there was 'Authenticating' sign even during loading metadata.
Now while data are loading there is 'Loading data' text. This change requires new global
topic 'set-activity' of activity widget. So for now there is possibility to change
every activity string during running phase just by publishing 'set-activity' topic
and setting new text as first parameter.

Part of: https://fedorahosted.org/freeipa/ticket/6144

Reviewed-By: Petr Vobornik <pvoborni@redhat.com>
2017-01-05 19:13:37 +01:00
..
certmonger Set explicit confdir option for global contexts 2016-12-02 09:14:35 +01:00
conf Build: remove incorrect use of MAINTAINERCLEANFILES 2016-11-16 09:12:07 +01:00
html Build: remove incorrect use of MAINTAINERCLEANFILES 2016-11-16 09:12:07 +01:00
migration Set explicit confdir option for global contexts 2016-12-02 09:14:35 +01:00
oddjob Set explicit confdir option for global contexts 2016-12-02 09:14:35 +01:00
restart_scripts Set explicit confdir option for global contexts 2016-12-02 09:14:35 +01:00
share adtrust: remove FILE: prefix from 'dedicated keytab file' in smb.conf 2016-12-12 16:39:32 +01:00
tools Clarify meaning of --domain and --realm in installers 2017-01-05 09:47:25 +01:00
ui Change activity text while loading metadata 2017-01-05 19:13:37 +01:00
updates Remove "Request Certificate with SubjectAltName" permission 2016-12-21 17:04:18 +01:00
wsgi Build: remove incorrect use of MAINTAINERCLEANFILES 2016-11-16 09:12:07 +01:00
Makefile.am Build: remove incorrect use of MAINTAINERCLEANFILES 2016-11-16 09:12:07 +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.