You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First up, I LOVE this package. It's making our development so much faster. One question I had was what would be a "best practice" for developing a DOCKER that we want to tune gunicorn (which I understand functions-framework uses as long as --debug isn't invoked). Say I have a line in my dockerfile:
CMD exec functions-framework --target=mycode
Is there some way to pass along the gunicorn tuning parameters to this statement? If not, what would be the correct way of adjusting e.g. threads and workers. Do I need to replace this entire line with e.g.
First up, I LOVE this package. It's making our development so much faster. One question I had was what would be a "best practice" for developing a DOCKER that we want to tune gunicorn (which I understand functions-framework uses as long as --debug isn't invoked). Say I have a line in my dockerfile:
CMD exec functions-framework --target=mycode
Is there some way to pass along the gunicorn tuning parameters to this statement? If not, what would be the correct way of adjusting e.g. threads and workers. Do I need to replace this entire line with e.g.
CMD exec gunicorn --bind :$PORT --workers 1 --threads 8 --timeout 0 main:app ?
The text was updated successfully, but these errors were encountered: