The apache configuration files must have, at a minimum, a WSGIScriptAlias directive.
There is also a list of the apache modules which get loaded, and mod_wsgi must be included. mod_wsgi must be linked against the particular apache, but the distribution, if you're using the OS's package manager, should have made sure of that. As previously mentioned by another, mod_wsgi is linked against a particular python interpreter. Again, hopefully the OS package manager pulls in stuff built to work together, but this does mean that you can't, say, use python2.7 if the distribution's python is a 2.6. It is much to be preferred, though not absolutely required, that the python in question was build after passing "--enable-shared" to the configure script. Unless you build everything yourself (which I usually do, but not yet on Raspberry PI), you have no control of this. That WSGIScriptAlias directive should probably specify a python-path argument specifying the directory with manage.py in it, though I've seen it work with the adding of this path deferred to the wsgi script python module. You can use a virtualenv, but it must have been made with the python interpreter against which mod_wsgi is linked (not the same file, but ve/bin/python is generally a copy, and this works well enough), but you will either need to use the WSGIPythonHome directive, or, if your mod_wsgi is new enough, the python-home argument of the WSGIScriptAlias directive. (The advantage of the latter is the ability to use separate virtualenvs in separate VirtualHosts, whereas WSGIPytonHome is global across all mod_wsgi daemon processes under a single apache..) You will want to configure Alias directives to allow serving your STATIC and MEDIA files at the expected URLs. You will need a number of Directory directives (though fewer than some people think). The mod_wsgi documentation is excellent. If you think otherwise it is because you don't yet appreciate the complexity of the issues. Bill On Thu, Jan 10, 2013 at 3:27 PM, <7equivale...@gmail.com> wrote: > When you say "From there it should just be configuration." Do you mean > either (1) Configuring mod-wsgi to work with apache, or (2) Configuring > mod_wsgi to work with Django. > > The errors where involved with my first attempt at installing mod-wsgi > according to the Django instructions, However now I'm using *sudo apt-get > install libapache2-mod-wsgi *which is not mentioned in the Django docs. > And step (3) seems to do whatever it does just fine with no errors. > > I'm not sure if I should be focusing on configuring mod-wsgi to work with > apach or configuring mod-wsgi to work with Django. I'm sure there are steps > for both that need to be taken.... > > > On Thursday, January 10, 2013 2:53:35 PM UTC-5, Nikolas Stevenson-Molnar > wrote: > >> From there, it should just be configuration. What errors are you seeing? >> >> _Nik >> >> On 1/10/2013 10:59 AM, 7equiv...@gmail.com wrote: >> > Hello, I need help configuring the Apache production server to work >> > with Django on a Rapberry pi. I am still new to Linux. Here is what >> > I've done so far. >> > >> > (1) I have successfully installed Apache on my Raspberry pi. I have >> > used it to serve up php webpages. >> > (2) I have successfully installed Django on the RaspPi and created a >> > project that works with the Django development server. >> > (3) I have run the command ~$ sudo apt-get install libapache2-mod-wsgi >> > >> > I am unsure where to proceed after step 3. Did step 3 install and >> > configure mod-wsgi to work with Apache, or do I still have some >> > initialization steps? Or, does the next step involve Django. I have >> > read and followed the steps from the Django website, but they produced >> > errors and where confusing to me. >> > >> > Any help would be greatly appreciated! >> > -- >> > You received this message because you are subscribed to the Google >> > Groups "Django users" group. >> > To view this discussion on the web visit >> > https://groups.google.com/d/**msg/django-users/-/**6SE8SJkDxf0J<https://groups.google.com/d/msg/django-users/-/6SE8SJkDxf0J>. >> >> > To post to this group, send email to django...@googlegroups.com. >> > To unsubscribe from this group, send email to >> > django-users...@**googlegroups.com. >> > For more options, visit this group at >> > http://groups.google.com/**group/django-users?hl=en<http://groups.google.com/group/django-users?hl=en>. >> >> >> -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/django-users/-/F8Bo4d3IP5oJ. > > To post to this group, send email to django-users@googlegroups.com. > To unsubscribe from this group, send email to > django-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
