IntenseWebs/freeipa
3
0
Fork 0
mirror of https://salsa.debian.org/freeipa-team/freeipa.git synced 2024-12-25 16:31:08 -06:00
Code Issues Packages Projects Releases Wiki Activity
49a5f14b47
freeipa/install
History
Endi S. Dewata 49a5f14b47 Added expand/collapse all. 
A link has been added into the details page to expand/collapse all
sections.

Previously each section's <div> container is identified using a long
ID. It is now identified using the section name.
2011-02-17 14:57:21 -05: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 Fix migration page 2011-02-11 13:28:22 -05:00
po Removed 'name' from 'Sudo Command Group name'. 2011-01-24 13:33:00 -05:00
share Browser configuration support for Firefox 4 2011-02-17 12:12:23 -05:00
tools Note --ip-address parameter of ipa-replica-prepare in man page 2011-02-15 15:42:27 -05:00
ui Added expand/collapse all. 2011-02-17 14:57:21 -05:00
updates Updated default Kerberos password policy 2011-02-16 22:28:08 -05: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

README.schema 

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.