freeipa

mirror of https://salsa.debian.org/freeipa-team/freeipa.git synced 2024-12-28 18:01:23 -06:00

History

Endi S. Dewata f0f83a862e Refactored action panel and client area. To improve code readability and extensibility the containers for action panel and client area are now created in IPA.entity.setup(). The 'client area' has been renamed into 'content'. The IPA.facet.create() has been renamed to IPA.facet.create_content().		2011-04-11 16:03:30 +00: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	Update translation file (ipa.pot).	2011-03-18 14:59:34 -04:00
share	Fix ORDERING in some attributetypes and remove other unnecessary elements.	2011-04-05 21:46:32 -04:00
tools	Fix typo in ipa-server-install.	2011-04-08 09:27:01 +02:00
ui	Refactored action panel and client area.	2011-04-11 16:03:30 +00:00
updates	Add memberHost and memberUser to default indexes	2011-04-08 11:00:24 -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

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.