Actions
Issue #3618
closed
Issue #3981: Switch Pulp3 settings to Dynaconf
database configuration docs are confusing
Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Documentation
Sprint:
Quarter:
Description
The install docs here:
say: Databases can be configed in the databases section of your server.yaml. See the Django database settings documentation for more information on setting the databases values in settings.yam
Yet the syntax presented in the django documentation is different than that in server.yaml. The differences include commas vs no commas, quotes vs no quotes, (yaml vs python) and there seems to be an OPTIONS hash in the example that isn't used for postgresql but is used for sqlite?
Some of this may be less confusing when the defaults are closer to what i wanted (i.e. postgresql), but if the syntax isn't the same i'd suggest not relying on django docs.
Actions
.
Problem: Pulp can't be configured using environment variables
Solution: use dynaconf to manage all of Pulp configuration settings
This patch also adds pulpcore.rqconfig module that is dynamically generated from the Django settings generated by dynaconf. The rq workers use this module for their configuration.
The default location of the config file is now at
/etc/pulp/settings.py. Pulp can operate without by relying on environment variables.closes: #3981 https://pulp.plan.io/issues/3981
closes: #3879 https://pulp.plan.io/issues/3879
closes: #3980 https://pulp.plan.io/issues/3980
closes #3618 https://pulp.plan.io/issues/3618
closes: #3943 https://pulp.plan.io/issues/3943