Issue #3981
Updated by bmbouter about 6 years ago
h3. Problem The .yaml format for the settings file is creating several challenges: * Users will have to have a separate Python file anyway for RQ. See https://pulp.plan.io/issues/3980 * We point users to the "Django docs" but all of those examples are for Python formatted configs. The user then has to translate these back to Yaml. This creates tickets like this: https://pulp.plan.io/issues/3618#note-3 * You can interpret runtime variables in Python, resolving issues like this: https://pulp.plan.io/issues/3943#note-3 * We can still support top-level "overwriting" by having the module settings overwrite default ones. That would resolve this: https://pulp.plan.io/issues/3879 h3. Proposal: Have Pulp use the Dynaconf Django: plugin.https://dynaconf.readthedocs.io/en/latest/guides/django.html#settings-files Users would still specify DJANGO_SETTINGS_MODULE=pulpcore.app.settings but dynaconf would be overlaying settings from a dynaconf config file or from environment variables. This would give us environment variable support and allow some installs to run without any config file at all. Also Update the docs need updating so the users know they can use dynaconf to configure Pulp with and to refer to their docs. with.
.