freeipa

0 Fork 0

Files

T

Christian Heimes b7700b9c5e Improve wsgi app loading

* move WSGI app code to main code base so it can be used with other
  WSGI servers that expect a Python package.
* populate LDAP schema early to speed up first request by ~200ms
* gc.collect() and gc.freeze() to improve memory handling and GC

Signed-off-by: Christian Heimes <cheimes@redhat.com>
Reviewed-By: Alexander Bokovoy <abokovoy@redhat.com>

2021-04-07 12:40:30 -04:00

certmonger

Improve performance of ipa-server-guard

2020-08-19 13:59:11 -04:00

custodia

Replace PYTHONSHEBANG with valid shebang

2019-06-24 09:35:57 +02:00

html

Change FreeIPA references to IPA and Identity Management

2021-02-09 09:48:23 -05:00

migration

Change FreeIPA references to IPA and Identity Management

2021-02-09 09:48:23 -05:00

oddjob

use a constant instead of /var/lib/sss/keytabs

2021-01-22 21:10:58 -05:00

restart_scripts

Don't create log files from help scripts

2019-09-24 15:23:30 +02:00

Improve wsgi app loading

2021-04-07 12:40:30 -04:00

tools

pylint: Fix several warnings

2021-03-30 13:18:09 +03:00

Also use uglifyjs on CentOS Stream 8

2021-04-02 09:51:55 +02:00

updates

ipasam: implement PASSDB getgrnam call

2021-01-22 21:10:58 -05:00

wsgi

wgi/plugins.py: ignore empty plugin directories

2020-11-06 16:38:37 -05:00

Makefile.am

Move Custodia secrets handler to scripts

2019-04-26 12:09:22 +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.