mod-wsgi

I have a folder called python2.7 inside of lib in the virtual environment. After reading half a dozen tutorials, I can't figure out exactly what I'm suppose to point the WSGIPythonPath to. I've seen some pointing to site-packages but some have been a colon : separated list. Syntax error on line 1019 of /etc/httpd/conf/httpd.conf: WSGIPythonPath cannot occur within <VirtualHost> section Where should WSGIPythonPath point in my virtualenv? You are getting the error because WSGIPythonPath Directive cannot be used inside the VirtualHost context. You have to declare it inside your main Apache

I've got my Apache server setup and it is handling Flask responses via mod_wsgi. I've registered the WSGI script via the alias: [httpd.conf] WSGIScriptAlias /service "/mnt/www/wsgi-scripts/service.wsgi" I've added the corresponding WSGI file at the above path: [/mnt/www/wsgi-scripts/service.wsgi] import sys sys.path.insert(0, "/mnt/www/wsgi-scripts") from service import application And I have a simple test Flask Python script that provides the service module: [/mnt/www/wsgi-scripts/service.py] from flask import Flask app = Flask(__name__) @app.route('/') def application(environ, start_response

I know that there are already a lot of information on this topic, but they are quite clumsy, not so simple and expressive. Could anyone explain me how to use django and with mod_wsgi and apache ? mod_wsgi isn't particularly the best fit for running Python WSGI applications, or, if you'd rather, there are more pythonic ways you can run your Django instance. First off, I'd reason that it takes a lot of effort to understand Apache's request processing model and to configure it correctly, especially with respect to mod_wsgi. If your not exactly set or locked into using Apache, I would recommend

What could be causing this error: $ sudo tail -n 100 /var/log/apache2/error.log' [Wed Dec 29 15:20:03 2010] [error] [client 220.181.108.181] mod_wsgi (pid=20343): Exception occurred processing WSGI script '/home/username/public_html/idm.wsgi'. [Wed Dec 29 15:20:03 2010] [error] [client 220.181.108.181] IOError: failed to write data Here is the WSGI script: $ cat public_html/idm.wsgi import os import sys sys.path.append('/home/username/public_html/IDM_app/') os.environ['DJANGO_SETTINGS_MODULE'] = 'settings' import django.core.handlers.wsgi application = django.core.handlers.wsgi.WSGIHandler()

When I update the code on my website I (naturally) restart my apache instance so that the changes will take effect. Unfortunately the first page served by each apache instance is quite slow while it loads everything into RAM for the first time (5-7 sec for this particular site). Subsequent requests only take 0.5 - 1.5 seconds so I would like to eliminate this effect for my users. Is there a better way to get everything loaded into RAM than to do a wget x times (where x is the number of apache instances defined by ServerLimit in my http.conf) Writing a restart script that restarts apache and

I am a bit confused about multiproessing feature of mod_wsgi and about a general design of WSGI applications that would be executed on WSGI servers with multiprocessing ability. Consider the following directive: WSGIDaemonProcess example processes=5 threads=1 If I understand correctly, mod_wsgi will spawn 5 Python (e.g. CPython) processes and any of these processes can receive a request from a user. The documentation says that: Where shared data needs to be visible to all application instances, regardless of which child process they execute in, and changes made to the data by one application