lili
/
Tlapbot
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases 6 Wiki Activity

add example of running log level debug w/ gunicorn

This commit is contained in:
Lili (Tlapka) 2022-11-25 16:35:39 +01:00
parent af36ddff75
commit b5c3a3c930
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -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. 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, **⚠️WARNING:** Because of the way the scheduler is initialized in the project,
I recommend running tlapbot with only one gunicorn worker. (`-w 1`) I recommend running tlapbot with only one gunicorn worker. (`-w 1`)