[modwsgi] fedora30, mod_wsgi, django
Hi, I posted recently asking has anyone worked with django under fedora30 as production server, with apache django mod_wsgi? I continued working and found this info very helpful: https://www.ionos.com/community/hosting/python/use-mod-wsgi-to-run-python-as-a-web-application-on-centos-7/ Where centos-7 info is also useful for fedora. The main Fedora issue, I think, is the way apache or httpd is implemented which favors the fedora repo version of mod_wsgi for install as opposed to one you build yourself due to the various install locations, config files, and system requirements. Once I got mod_wsgi installed and verified working running a .wsgi file, I was able to tackle the problem of where the django app lives. The article above shows how to get started with the location, file/folder permissions and owerships by serving a .py script using mod_wsgi. Next step for me is trying to get my django app working using a similar approach, having the httpd.conf file work for a virtualhost, and running it with nip.io since I have conflicting ports on my production machine with existing apps. Thanks, bob -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To unsubscribe from this group and stop receiving emails from it, send an email to modwsgi+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/modwsgi/CALWZDaMT4A81fHxeHdspk66VAFdLHqhsE%3DVYvaKgTXPwOOQ-Qg%40mail.gmail.com.
Re: [modwsgi] Server-Sent Events (SEE) blocking all threads
> On 6 Aug 2019, at 21:03, Orestis Zambounis > wrote: > > Many thanks. I'm going to dive into gunicorn, gevents etc. > As I am deploying to Elastic beanstalk which is set up with Apache/mod_wsgi > by default would you recommend to look into switching the server to gunicorn > or use some other strategy for real-time communication such as sockets in > terms of effort (given that I have no knowledge about setting up gunicorn or > websockets) instead? Do websockets present the same problems as SSE in my > usecase for mod_wsgi? Yes they do and websockets likely will not even work at all. You are better off using an async server and not wsgi for this use case. Graham > > -- > You received this message because you are subscribed to the Google Groups > "modwsgi" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to modwsgi+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/modwsgi/d98597b5-fce7-42ec-ae01-6f0d154ac810%40googlegroups.com. -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To unsubscribe from this group and stop receiving emails from it, send an email to modwsgi+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/modwsgi/5AE88B1C-7273-4621-9084-DB15C5567748%40gmail.com.
Re: [modwsgi] Server-Sent Events (SEE) blocking all threads
Many thanks. I'm going to dive into gunicorn, gevents etc. As I am deploying to Elastic beanstalk which is set up with Apache/mod_wsgi by default would you recommend to look into switching the server to gunicorn or use some other strategy for real-time communication such as sockets in terms of effort (given that I have no knowledge about setting up gunicorn or websockets) instead? Do websockets present the same problems as SSE in my usecase for mod_wsgi? -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To unsubscribe from this group and stop receiving emails from it, send an email to modwsgi+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/modwsgi/d98597b5-fce7-42ec-ae01-6f0d154ac810%40googlegroups.com.
