These are chat archives for fossasia/open-event-server

11th
Apr 2017
Amol Mejari
@mejariamol
Apr 11 2017 03:17
@Himanshi-Khandelwal thank you. But it was my proxy issue. setting all_proxy to https.. solved the issue.. :smile:
Mario Behling
@mariobehling
Apr 11 2017 07:54
A lot of new people are joining FOSSASIA development currently. I have put together best practices we have learned over the last few years to help us working together. Please check it out: https://twitter.com/mariobehling/status/851703793431588864
Avi Aryan
@aviaryan
Apr 11 2017 08:30
:+1: Nice, comprehensive article.
Amol Mejari
@mejariamol
Apr 11 2017 12:30
need some help..
while using gunicorn server to run,
on gunicorn app:app --worker-class eventlet -w 1 --bind 0.0.0.0:5000 --reload
gives error-raise RuntimeError('no suitable implementation for this system') RuntimeError: no suitable implementation for this system [2017-04-11 17:54:13 +0000] [5058] [INFO] Worker exiting (pid: 5058) [2017-04-11 17:54:13 +0000] [5053] [INFO] Shutting down: Master [2017-04-11 17:54:13 +0000] [5053] [INFO] Reason: Worker failed to boot.
Nguyễn Hồng Quân
@hongquan
Apr 11 2017 15:21
@mejariamol
Any reason why you run gunicorn with eventlet? How about default backend?
Amol Mejari
@mejariamol
Apr 11 2017 16:28

@hongquan websockets not supported on default right..

The development server is the one that Flask ships with. It's based on Werkzeug and does not support WebSockets. If you try to run it, you'll get a RunTime error, something like: You need to use the eventlet server.. To test real-time notifications, you must use the Gunicorn web server with eventlet worker class.