-
-
Notifications
You must be signed in to change notification settings - Fork 330
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Debug mode? #3
Comments
just create a env GUNICORN_CMD_ARGS="--reload" http://docs.gunicorn.org/en/stable/settings.html#reload or you can insert into gunicorn-conf.py
|
Aarrgghhh! Yes that works great - read somewhere that didn’t work and didn’t test it. Shame on me. Thanks! Thanks also for the env tip - works great with Docker compose. |
Awesome! I'm glad it's working for you. @rudmac Thanks for your help here! It's very appreciated. 👏 🌮 There's a new integrated script It runs only Uvicorn with Check the updated docs here: https://github.com/tiangolo/uvicorn-gunicorn-fastapi-docker#development-live-reload |
Thanks - I'll update the writeup I made for it: https://medium.com/@williamhayes/fastapi-starlette-debug-vs-prod-5f7561db3a59 (future note for myself (ever searched for a solution to a problem and find an old post with the answer - still undecided if it is embarrassing or an example of impressive forethought)) FYI - looks like --reload and --debug are equivalent currently in uvicorn. I'll make a note of that as well. |
Thanks! And great post! In Uvicorn, Check: fastapi/fastapi#66 |
I have tried
and this
not working in VSCode |
Can reloading be working without a gunicorn? |
Not easily without either |
Trying to figure out how to turn on auto-reloading (e.g. debug mode) while using docker. I develop in the docker container by volume mounting the app directory into the docker container so any changes I make to the code are available immediately inside the running docker container. I can't figure out how to start debug mode using gunicorn with uvicorn.
Any ideas?
PS Great project and thanks!
The text was updated successfully, but these errors were encountered: