IntenseWebs/freeipa
3
0
Fork 0
mirror of https://salsa.debian.org/freeipa-team/freeipa.git synced 2024-12-28 18:01:23 -06:00
Code Issues Packages Projects Releases Wiki Activity
313f201ea5
freeipa/install
History
Endi S. Dewata 313f201ea5 Merged direct and indirect association facets 
The direct and indirect associations are now displayed in the same
facet. The type of association to be displayed can be selected
using radio buttons.

Ticket #1338
2011-06-16 20:11:22 -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 Add port 9443 to replica port checking 2011-06-15 17:22:10 +02:00
ui Merged direct and indirect association facets 2011-06-16 20:11:22 -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

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.