freeipa/install
Endi S. Dewata 9704adfe44 Fixed resizing issues.
The UI has been modified to fix some resizing issues:

Previously the height of facet content was roughly calculated using
resize(). Now the height can be more accurately defined in CSS.

Previously the UI width was fixed. The HTML layout and background
images have been modified to support horizontal expansion if needed.
2011-06-13 09:23:29 -04:00
..
conf rename static to ui 2011-01-20 14:12:47 +00:00
html error handling style 2011-01-25 16:47:09 -05:00
migration Use ldapi: instead of unsecured ldap: in ipa core tools. 2011-03-03 14:04:34 -05:00
po Connection check program for replica installation 2011-06-08 09:29:52 +02:00
share Remove root autobind search restriction, fix upgrade logging & error handling. 2011-06-13 09:51:05 +02:00
tools Fix directory manager password validation in ipa-nis-manage. 2011-06-13 12:59:22 +02:00
ui Fixed resizing issues. 2011-06-13 09:23:29 -04:00
updates Configure Managed Entries on replicas. 2011-05-25 16:39:27 -04:00
configure.ac rename static to ui 2011-01-20 14:12:47 +00:00
Makefile.am rename static to ui 2011-01-20 14:12:47 +00: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.