From b5c3a3c930b15f4768f860b58fd51363f7a48f00 Mon Sep 17 00:00:00 2001 From: Lili Date: Fri, 25 Nov 2022 16:35:39 +0100 Subject: [PATCH] add example of running log level debug w/ gunicorn --- README.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/README.md b/README.md index b7a0de5..d5bcc52 100644 --- a/README.md +++ b/README.md @@ -178,6 +178,10 @@ gunicorn -w 1 'tlapbot:create_app()' You should also set `GUNICORN` in your `config.py` file to `True` to see Tlapbot logs in your gunicorn output. By default, gunicorn will only show `error` and `critical` warnings, but you can set the `--log-level` argument when running the app to set it to `warning`, `debug` or `info` too. +```bash +gunicorn -w 1 --log-level debug 'tlapbot:create_app()' +``` + **⚠️WARNING:** Because of the way the scheduler is initialized in the project, I recommend running tlapbot with only one gunicorn worker. (`-w 1`)