Skip to content
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

Go back to using gunicorn #206

Closed
bmispelon opened this issue Dec 1, 2014 · 3 comments
Closed

Go back to using gunicorn #206

bmispelon opened this issue Dec 1, 2014 · 3 comments

Comments

@bmispelon
Copy link
Contributor

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?

@d0ugal
Copy link

d0ugal commented Dec 1, 2014

Sounds like a good move to me.

@olasitarska
Copy link
Member

oh yeah! 👍 😂

@keimlink
Copy link
Contributor

Good proposal! 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants