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

The Deployment section of the docs #1409

Open
arjunsatarkar opened this issue Feb 16, 2023 · 2 comments
Open

The Deployment section of the docs #1409

arjunsatarkar opened this issue Feb 16, 2023 · 2 comments

Comments

@arjunsatarkar
Copy link

arjunsatarkar commented Feb 16, 2023

Deployment lists many server backends. Here are some which seem defunct and thus IMO not really suited to running a production web server.

flup - website down.
cherrypy - site replaced with some SEO spam blog?
paste - site parked/redirects to some ads.
rocket - last commit 2017, almost 6 years ago.
diesel - site blank, or possibly ad-ridden, I'm not sure since I block ads.
fapws3 - last commit 2017, almost 6 years ago.
meinheld - site is now an SEO spam blog, last commit 2020.

I realise the code might work, but given that the web tends to change, I would not be surprised if some part of these were to suddenly break in the future (or already have). Plus, there is not going to be any hope of reporting any extant issues - including security issues. So it is probably best to remove them.

Also, a minor note - eventlet's site supports HTTPS but does not redirect HTTP to HTTPS. Bottle docs links to the HTTP version. It would be better if they linked to the HTTPS version.

Anyway, that decimates the entire multi-threaded section except Waitress. So I have a question about the asynchronous ones. The docs say they "can get a bit tricky" and you "need to design your application accordingly", but it's hard to find resources regarding what one needs to do to use, say, tornado effectively with bottle. It would be nice if the docs said something more specific about this.

@premins
Copy link

premins commented Mar 24, 2023

CherryPy should be https://cherrypy.dev/

@valq7711
Copy link

"can get a bit tricky" - I think this is a general remark about any asynchronous code.
WSGI is not async by its nature, there is only one easy way to make WSGI app to work as async-like - use gevent with monkey patching (it is a bit hacky).
If you really need async app - you'd better look at FastAPI

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

No branches or pull requests

3 participants