summaryrefslogtreecommitdiff
path: root/issues
diff options
context:
space:
mode:
authorFrederick Muriuki Muriithi2023-04-04 10:17:13 +0300
committerFrederick Muriuki Muriithi2023-04-04 10:17:13 +0300
commit2ffabbd5e86c8e46720c77c221827ea0c62e17a8 (patch)
tree7258a6746e704cde7dbec285765747e819a9ff5f /issues
parent5a3c74467fc9cab348e2a9776509e30fff945c2a (diff)
downloadgn-gemtext-2ffabbd5e86c8e46720c77c221827ea0c62e17a8.tar.gz
Provide links to possible fixes
Diffstat (limited to 'issues')
-rw-r--r--issues/bugfix_coupling_current_app_and_db_utils.gmi7
1 files changed, 7 insertions, 0 deletions
diff --git a/issues/bugfix_coupling_current_app_and_db_utils.gmi b/issues/bugfix_coupling_current_app_and_db_utils.gmi
index 2f27221..13956b4 100644
--- a/issues/bugfix_coupling_current_app_and_db_utils.gmi
+++ b/issues/bugfix_coupling_current_app_and_db_utils.gmi
@@ -29,3 +29,10 @@ by any settings provided via the `GN3_CONF` variable.
The issue here is that the value in `gn3.settings` can be fetched from the shell environment variables, overwriting any default value in `gn3.settings` but that can then be overwritten by `GN3_CONF`. This implies that we need a more traceable configuration system.
The scripts that use the same configuration values as the application should probably be run as **flask CLI** commands, or have the configuration variable(s) provided to the script(s) directly via the CLI.
+
+### Fix: Provide URI on the CLI
+
+Commits attempting to fix the issue
+
+=> https://github.com/genenetwork/genenetwork3/commit/d8c73f74a022540eec306399a4ad719089678579 in genenetwork3
+=> https://github.com/genenetwork/genenetwork-machines/commit/1fc0198aaf595719e9e5f1a182731073458c449e in genenetwork-machines