diff options
| author | BonfaceKilz | 2021-12-03 15:48:12 +0300 |
|---|---|---|
| committer | BonfaceKilz | 2021-12-03 15:48:12 +0300 |
| commit | c630ecb79cec6d22562f33566191034f3eaab8c3 (patch) | |
| tree | c4bc9070cfae8871a71ce55915f28160c0fdb95d | |
| parent | cbe94eb40a84a6a071f671d685d83284030d4cd8 (diff) | |
| download | gn-gemtext-c630ecb79cec6d22562f33566191034f3eaab8c3.tar.gz | |
Reference correct module
| -rw-r--r-- | issues/deploy.gmi | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/issues/deploy.gmi b/issues/deploy.gmi index f701805..94d73ec 100644 --- a/issues/deploy.gmi +++ b/issues/deploy.gmi @@ -5,10 +5,10 @@ hassle. In genenetwork2, our configs live in different places, and it takes some fiddling tinged with a bit of domain (gn2) knowledge to work out what setting live where. With the introduction of blueprints in our code-base, this duplication became a necessary evil because -most of the settings QC checks happen in a "utility/settings.py" which +most of the settings QC checks happen in a "utility/tools.py" which unfortunately imports the "app" object. This import leads to circular imports whenever we use blueprints. Unfortunately, a huge chunk of -the code base uses "utility/settings.py" to get configuration +the code base uses "utility/tools.py" to get configuration settings; and removing this would make gn2 as is disfunctional. # Tags |