IntenseWebs/freeipa
3
0
Fork 0
mirror of https://salsa.debian.org/freeipa-team/freeipa.git synced 2024-12-25 00:20:04 -06:00
Code Issues Packages Projects Releases Wiki Activity
5c054a77f3
freeipa/install
History
Petr Viktorin 1907f720d5 Pull translation files from Transifex 
Patch generated by:
  cd install/po
  make pull-po
  make update-po
2012-10-11 16:09:27 -04:00
..
certmonger Use DN objects instead of strings 2012-08-12 16:23:24 -04:00
conf Configure the initial CA as the CRL generator. 2012-10-09 19:24:43 -04:00
ffextension Kerberos authentication extension makefiles 2012-10-04 18:07:34 -04:00
html Removal of delegation-uris instruction from browser config 2012-10-04 18:35:47 -04:00
migration Use DN objects instead of strings 2012-08-12 16:23:24 -04:00
po Pull translation files from Transifex 2012-10-11 16:09:27 -04:00
restart_scripts Use Dogtag 10 only when it is available 2012-09-17 18:43:59 -04:00
share Explicitly disable betxn plugins for the time being. 2012-10-10 20:24:10 -04:00
tools Create Firefox extension on upgrade and replica-install 2012-10-10 17:34:19 +02:00
ui support multi-line error messages in exceptions 2012-10-09 10:18:40 +02:00
updates Explicitly disable betxn plugins for the time being. 2012-10-10 20:24:10 -04:00
configure.ac Kerberos authentication extension makefiles 2012-10-04 18:07:34 -04:00
Makefile.am Move CRL publish directory to IPA owned directory 2012-10-09 16:00:01 +02: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.