Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
[#2842] New CKAN config object, decoupled from Pylons #3163
This PR includes a bunch of changes that provide a common configuration object for CKAN that works both on Flask and Pylons.
Both Flask and Pylons config objects are dict-like objects with key/value configuration options. But the Flask one is bound to the application and so it's only available when there is an application context available. This means that it can not support the way in which we were using the Pylons config, which was essentially available everywhere, on the CLI, tests, etc. In order to not change completely the way the application is structured and how the configuration is accessed in all parts of the code it seemed a good approach to have our own dict-like config object that was available in the same way the Pylons config object is.
At the same time we don't want to have different sets of configurations for stuff relevant to CKAN, Flask or Pylons (eg
Moving forward this should be the only configuration object used in all code unless we really
Extensions should be encouraged to use