freeipa/install
Jan Cholasta cc53526fd2 Decode script arguments using file system encoding
This mimics Python 3's behavior, where sys.argv is automatically decoded
using file system encoding, as returned by sys.getfilesystemencoding(). This
includes reimplementation of os.fsdecode() from Python 3.

Reviewed-By: Petr Viktorin <pviktori@redhat.com>
2015-09-07 08:00:11 +02:00
..
certmonger Use the print function 2015-09-01 11:42:01 +02:00
conf Provide Kerberos over HTTP (MS-KKDCP) 2015-06-24 10:43:58 +02:00
ffextension webui: append network.negotiate-auth.trusted-uris 2014-09-11 09:41:51 +02:00
html webui: add Kerberos configuration instructions for Chrome 2015-07-27 13:50:49 +02:00
migration Replace dict.has_key with the 'in' operator 2015-08-12 18:17:23 +02:00
oddjob Decode script arguments using file system encoding 2015-09-07 08:00:11 +02:00
po Remove the unused pygettext script 2015-09-01 11:39:42 +02:00
restart_scripts cert renewal: Automatically update KRA agent PEM file 2015-08-27 15:53:42 +02:00
share Added CLI param and ACL for vault service operations. 2015-08-17 08:10:59 +02:00
tools Decode script arguments using file system encoding 2015-09-07 08:00:11 +02:00
ui webui: add option to establish bidirectional trust 2015-08-26 13:05:51 +02:00
updates trusts: harden trust-fetch-domains oddjobd-based script 2015-08-18 18:48:12 +02:00
wsgi Modernize 'except' clauses 2015-08-12 18:17:23 +02:00
configure.ac trusts: add support for one-way trust and switch to it by default 2015-07-08 01:56:52 +02:00
Makefile.am trusts: add support for one-way trust and switch to it by default 2015-07-08 01:56:52 +02: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.