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
We switched to waitress after having issues with gunicorn and ssl but it turned out later that those issues were most likely caused by heroku-push (19df845).
Now that we've ditched heroku-push, I think we should go back to gunicorn as well:
It has a better name (seriously, who though "waitress" was a good name!).
It doesn't polute the logs with its man page when you make a typo in your wsgi.py file.
What do you think?
The text was updated successfully, but these errors were encountered:
We switched to
waitress
after having issues withgunicorn
andssl
but it turned out later that those issues were most likely caused byheroku-push
(19df845).Now that we've ditched
heroku-push
, I think we should go back togunicorn
as well:wsgi.py
file.What do you think?
The text was updated successfully, but these errors were encountered: