freeipa/install
Petr Vobornik ca7cece133 WebUI build: replace uglifyjs with system package
UgligyJS is packaged in Fedora and other OSes it is no longer required
to carry our own version. This will lower the maintanance burden - the
code doesn't need to be updated and it is less code to have in repo.

On some configuration usage of the budled UglifyJS 1 produces
"JavaScript throw: java.lang.StackOverflowError" exception. Usage of more
recent version should fix it.

Reviewed-By: Armando Neto <abiagion@redhat.com>
2018-07-12 15:38:01 +02:00
..
certmonger Have all the scripts run in python 3 by default 2018-02-15 18:43:12 +01:00
html Address more 'to login' 2017-12-12 12:53:21 +01:00
migration Add absolute_import future imports 2018-04-20 09:43:37 +02:00
oddjob Have all the scripts run in python 3 by default 2018-02-15 18:43:12 +01:00
restart_scripts Cleanup shebang and executable bit 2018-07-05 19:46:42 +02:00
share Increase WSGI process count to 5 on 64bit 2018-06-15 13:02:53 +02:00
tools Fix DNSSEC install regression 2018-07-10 17:51:05 +02:00
ui WebUI build: replace uglifyjs with system package 2018-07-12 15:38:01 +02:00
updates Use replace instead of add to set new default ipaSELinuxUserMapOrder 2018-06-08 10:49:18 +02:00
wsgi Add absolute_import future imports 2018-04-20 09:43:37 +02:00
Makefile.am Encrypt httpd key stored on disk 2018-03-23 12:48:46 +01: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.