summaryrefslogtreecommitdiff
path: root/topics
diff options
context:
space:
mode:
authorFrederick Muriuki Muriithi2023-05-22 08:55:47 +0300
committerFrederick Muriuki Muriithi2023-05-22 08:55:47 +0300
commit47e4be153689b099d3005c4e7e33e0c6ffc53f03 (patch)
tree7578a88ff627aad6bfeef9987174624cf6010af0 /topics
parentf65abc2cd4cff4ddf42222fa3e1fea9254cc4722 (diff)
downloadgn-gemtext-47e4be153689b099d3005c4e7e33e0c6ffc53f03.tar.gz
Add missing example.
Diffstat (limited to 'topics')
-rw-r--r--topics/using-pdb-to-troubleshoot.gmi6
1 files changed, 6 insertions, 0 deletions
diff --git a/topics/using-pdb-to-troubleshoot.gmi b/topics/using-pdb-to-troubleshoot.gmi
index 4cfe616..294486f 100644
--- a/topics/using-pdb-to-troubleshoot.gmi
+++ b/topics/using-pdb-to-troubleshoot.gmi
@@ -116,6 +116,12 @@ the process, leading to the error above. Generally speaking, you **SHOULD NOT**
be running the debugger in production anyway, and therefore you should not need
to deal with the gunicorn issues.
+That said, you can start the Flask application under pdb with something like:
+
+```
+python3 -m pdb flask run [OPTIONAL-ARGUMENTS-TO-FLASK]
+```
+
## Useful Tutorials