freeipa/install
Petr Vobornik dec7f98aa9 webui: ContainerMixin
A mixin which implements widget storing logic. Similar logic is already implemented
in details facet and dialog.

Long term goal is to replace that with this one.

Separating the logic into mixin makes it usable in other components.

https://fedorahosted.org/freeipa/ticket/3903

Reviewed-By: Adam Misnyovszki <amisnyov@redhat.com>
2014-04-15 12:41:53 +02:00
..
certmonger Support exporting CSRs in dogtag-ipa-ca-renew-agent. 2014-03-25 16:54:56 +01:00
conf Use certmonger D-Bus API to configure certmonger in CA install. 2014-03-25 16:54:54 +01:00
ffextension Kerberos authentication extension makefiles 2012-10-04 18:07:34 -04:00
html Load updated Web UI files after server upgrade 2013-10-16 18:06:30 +02:00
migration Use IPAdmin rather than raw python-ldap in migration.py and ipadiscovery.py 2013-03-13 12:36:33 +01:00
po fix typo in ipa -v migrate-ds 2014-03-21 13:08:03 +01:00
restart_scripts Merge restart_httpd functionality to renew_ra_cert. 2014-03-25 16:54:55 +01:00
share schema-compat: set precedence to 49 to allow OTP binds over compat tree 2014-04-04 08:45:43 +02:00
tools Update certmonger configuration in ipa-upgradeconfig. 2014-03-25 16:54:56 +01:00
ui webui: ContainerMixin 2014-04-15 12:41:53 +02:00
updates Add managed read permissions to pwpolicy and cosentry 2014-04-14 12:05:40 +02:00
wsgi Generate plugin index dynamically 2013-05-06 16:22:30 +02:00
configure.ac RCUE initial commit 2014-01-21 12:04:02 +01:00
Makefile.am Change group ownership of CRL publish directory 2013-07-16 12:17:40 +02: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.