As a result of a hackathon project last fall, the "config-models" Django application moved from its location inside edx-platform to a separate repository here:
https://github.com/edx/django-config-models Implications of this change: - The edx-platform repository no longer has the config-models code - it's in the new repository and is installed as a separate Django application into edx-platform. - The config-models tests in the separate repo are no longer run for every edx-platform CI test cycle. - *config-models can now be used in your favorite Django application*. These models offer the following features: - Django models backed by storage backend - Editable in the Django admin interface - Represent individual configuration values checked at run-time - Enabled/disabled values - Audit trail of who changed the values and when they were changed To learn more about config-models and how they might help your application manage configuration, search for "ConfigurationModel" in the edx-platform codebase and see the README here: https://github.com/edx/django-config-models/blob/master/README.rst The commit history of the code was not carried over to the new repository. To see the previous commit history for the code, check here: https://github.com/edx/edx-platform/commits/release-2016- 10-12/common/djangoapps/config_models FYI, John -- You received this message because you are subscribed to the Google Groups "General Open edX discussion" group. To view this discussion on the web visit https://groups.google.com/d/msgid/edx-code/CAJtBG53M9c22vBKovS5_%3DVWCzNvg6HFRV3x_h3HJTNbvypHfzg%40mail.gmail.com.
