freeipa/install
Rob Crittenden 4fd20966f6 Improved handling for ipa-pki-proxy.conf
- Remove ipa-pki-proxy.conf when IPA is uninstalled
- Move file removal to httpinstance.py and use remove_file()
- Add a version stanza
- Create the file if it doesn't exist on upgraded installs

https://fedorahosted.org/freeipa/ticket/1771
2011-09-13 16:09:15 +02:00
..
conf Improved handling for ipa-pki-proxy.conf 2011-09-13 16:09:15 +02:00
html Fixed browser configuration pages 2011-08-17 17:28:25 +00:00
migration Fixed broken links in ipa_error.css and ipa_migration.css. 2011-08-11 13:38:36 +00:00
po ticket 1669 - improve i18n docstring extraction 2011-08-24 23:13:16 -04:00
share Move Managed Entries into their own container in the replicated space. 2011-09-12 16:28:27 -04:00
tools Improved handling for ipa-pki-proxy.conf 2011-09-13 16:09:15 +02:00
ui Fixed missing optional field. 2011-09-13 05:52:05 +00:00
updates Move Managed Entries into their own container in the replicated space. 2011-09-12 16:28:27 -04:00
configure.ac ticket 1650 - compute accurate translation statistics 2011-08-18 14:25:58 +02: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.