Setup django-configglue
Bug #674115 reported by
Michael Nelson
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ratings and Reviews server |
Fix Released
|
Medium
|
Anthony Lenton | ||
Bug Description
We should setup django-configglue for all settings etc., but while there, there are some constants throughout the code that we'll need to extract to the configuration (so that we can use different values for testing, staging, production etc.). One that I've noticed (it might be the only one) authorizer.
| tags: | added: proj-rnr-10.12 |
Revision history for this message
| Anthony Lenton (elachuni) wrote | #1 |
| Changed in rnr-server: | |
| assignee: | nobody → Anthony Lenton (elachuni) |
| status: | Confirmed → In Progress |
| Changed in rnr-server: | |
| status: | In Progress → Fix Committed |
| tags: | added: kb-defect |
| tags: | added: qa-untestable |
| Changed in rnr-server: | |
| status: | Fix Committed → Fix Released |
| Changed in rnr-server: | |
| milestone: | none → 11.01 |
| Changed in rnr-server: | |
| milestone: | 11.01 → 10.12 |
To post a comment you must log in.
authorizer.
As far as I've seen it was the only hardcoded constant, but there might be others.
Setting up configglue still remains.