freeipa

0 Fork 0

Files

T

Martin Babinsky a2de6a17c5 Move tmpfiles.d configuration handling back to spec file

Since ipaapi user is now created during RPM install and not in runtime,
we may switch back to shipping tmpfiles.d configuration directly in RPMs
and not create it in runtime, which is a preferred way to handle drop-in
configuration anyway.

This also means that the drop-in config will be shipped in /usr/lib
instead of /etc according to Fedora packaging guidelines.

This partially reverts commit 38c66896de.

https://pagure.io/freeipa/issue/7053

Reviewed-By: Tibor Dudlak <tdudlak@redhat.com>

2017-08-30 13:05:23 +02:00

certmonger

certmonger: remove temporary workaround

2017-08-30 12:55:59 +02:00

conf

Changing cert-find to go through the proxy instead of using the port 8080

2017-06-16 08:56:53 +02:00

html

fix spelling mistake; minor rewording

2017-05-19 09:52:46 +02:00

migration

logging: do not log into the root logger

2017-07-14 15:55:59 +02:00

oddjob

wsgi, oddjob: remove needless uses of Env

2017-07-14 15:55:59 +02:00

restart_scripts

Fix Certificate renewal (with ext ca)

2017-08-30 12:58:58 +02:00

Move tmpfiles.d configuration handling back to spec file

2017-08-30 13:05:23 +02:00

tools

py3: remove Exception.message appearances

2017-08-29 12:55:25 +02:00

WebUI: fix incorrectly shown links in association tables

2017-08-17 10:10:21 +02:00

updates

Fix ipa-server-upgrade: This entry already exists

2017-08-30 12:47:53 +02:00

wsgi

logging: do not log into the root logger

2017-07-14 15:55:59 +02:00

Makefile.am

Configure HTTPD to work via Gss-Proxy

2017-02-15 07:13:37 +01: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.