IntenseWebs/freeipa
3
0
Fork 0
mirror of https://salsa.debian.org/freeipa-team/freeipa.git synced 2025-02-25 18:55:28 -06:00
Code Issues Packages Projects Releases Wiki Activity
a1c690cc02
freeipa/install
History
Endi S. Dewata bb31d3df21 Fixed problem clicking 3rd level tabs. 
The 3rd level tabs were partially covered by the content panel, so
only the top portion can be clicked. The content panel has been
repositioned to avoid the problem.
2011-08-11 18:40:54 +00:00
..
conf rename static to ui 2011-01-20 14:12:47 +00:00
html Redirection after changing browser configuration 2011-08-08 13:49:26 -04:00
migration Fixed broken links in ipa_error.css and ipa_migration.css. 2011-08-11 13:38:36 +00:00
po Make dogtag an optional (and default un-) installed component in a replica. 2011-06-23 19:04:33 -04:00
share Redirection after changing browser configuration 2011-08-08 13:49:26 -04:00
tools Ask for reverse DNS zone information in attended install right after asking for DNS forwarders, so that DNS configuration is done in one place. 2011-08-09 13:12:19 +02:00
ui Fixed problem clicking 3rd level tabs. 2011-08-11 18:40:54 +00:00
updates Correct sudo runasuser and runasgroup attributes in schema 2011-07-19 08:06:41 -04:00
configure.ac Removed custom layouts using HTML templates. 2011-07-21 11:47:57 -04: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.