Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Feature: Disable access log when using live-reload #177

Closed
RafaelWO opened this issue Mar 28, 2023 · 1 comment
Closed

Feature: Disable access log when using live-reload #177

RafaelWO opened this issue Mar 28, 2023 · 1 comment

Comments

@RafaelWO
Copy link

When using gunicorn (via start.sh), one can disable the API access log via setting the corresponding environment variable to an empty value: ACCESS_LOG=. However, this is not possible when running the app with uvicorn and live-reload (via start-reload.sh).

But since you can pass the option --no-access-log to uvicorn (see docs), the script could be extended to disable the access log if the variable is set to an empty value.

@tiangolo
Copy link
Owner

Now that Uvicorn supports managing workers with --workers, including restarting dead ones, there's no need for Gunicorn. That also means that it's much simpler to build a Docker image from scratch now, I updated the docs to explain it.

Because of that, I deprecated this Docker image: https://github.com/tiangolo/uvicorn-gunicorn-docker#-warning-you-probably-dont-need-this-docker-image

That also means that all the configurations are much simpler as you only need to deal with Uvicorn, not with Gunicorn on top. 😎

Repository owner locked and limited conversation to collaborators Aug 25, 2024
@tiangolo tiangolo converted this issue into discussion #233 Aug 25, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants