-
Notifications
You must be signed in to change notification settings - Fork 118
Document ability to use Functions Framework as a WSGI app #43
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
Comments
Sorry to lurk onto this - but the example Dockerfile's use of Additionally, using
Is using |
Is it possible you're using an older version of the repo, or an older version of the framework, or have some of the Docker layers cached? Since version Building the example
Note that there is no warning and that it invokes gunicorn. |
Ahhh - I think the confusion was that the root README recommends we run After I saw the warning message and how the cloud run http example README says to use gunicorn but the Dockerfile uses
So I guess the answer to my question is, Apologies for the confusion! |
Closing as stale. i don't think we're going to do this anytime soon, but if someone wants to make a PR to the README.md I'll happily review |
While #36 removed the example of fine-tuning gunicorn, it's still possible to use the Functions Framework as a WSGI app in this way.
We should document how to do this if you need finer control over the HTTP server used, and also document some other WSGI servers that users could use instead of gunicorn if they need to.
The text was updated successfully, but these errors were encountered: