freeipa/install
Adam Young 7486a33221 scrollable content areas
Turn off the side scroll bars for pages.

Resizes the table when the browser resizes

For stables, the rows scroll, but not the header.
For details, the content area scrolls.
Reserves 400 picesl for the header/ footer.   Resize is only done on reload
2011-06-02 14:28:24 -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 Several improvements of the lint script. 2011-05-05 11:54:07 +02:00
share Configure Managed Entries on replicas. 2011-05-25 16:39:27 -04:00
tools Honor netmask in DNS reverse zone setup. 2011-05-30 13:37:03 +02:00
ui scrollable content areas 2011-06-02 14:28:24 -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.