Not sure what would happen inside a virtual environment, or if it were run outside of sudo. When it is run outside of a virtual environment:
sudo mod_wsgi-express install-module Will copy the .so up into the apache2 directory: /usr/lib/apach2/modules/mod_wsgi-py27.so So it is in the proper location for running under the apache2 daemon. The trick to all of this is that apache2 has a naming convention such that the mod_XXX.so module name in that directory must match the filename in the mods-available directory (XXX.conf, XXX.load). On Mon, Oct 26, 2015 at 5:19 PM, Graham Dumpleton < [email protected]> wrote: > Great to here it worked. Hope you found the pip/install-module approach > somewhat easier. > > Just be aware that if you pip installed mod_wsgi into a Python virtual > environment, that the WSGIPythonHome directive you would have added based > on what install-module told you, will be to the virtual environment. So > make sure you don’t go blowing away the virtual environment and not > recreating it as mod_wsgi will still be trying to reference it for run time > Python installation. > > Graham > > On 27 Oct 2015, at 11:14 am, Mitch Sundt <[email protected]> wrote: > > Oops. I forgot > > sudo a2enmod wsgi-py27 > > before the restart of the server. > > > > On Mon, Oct 26, 2015 at 5:12 PM, Mitch Sundt <[email protected]> > wrote: > >> Ah, the install-module is what I was missing... >> >> (I didn't want to build from source if I could help it). >> >> For those wanting to upgrade via this hybrid approach, on Ubuntu, these >> are the steps I took: >> >> # don't think these are needed in this approach, but I had done them >> earlier >> >> sudo apt-get install apache2-mpm-worker >> sudo apt-get install apache2-threaded-dev >> >> # install wsgi via the Python mechanism >> >> sudo pip install mod_wsgi >> >> # stop the server >> >> sudo /etc/init.d/apache2 stop >> >> # copy the old wsgi config to the new 4.x filenames >> >> cd /etc/apache2/mods-available >> sudo cp wsgi.conf wsgi-py27.conf >> sudo cp wsgi.load wsgi-py27.load >> >> # remove the old 3.x mod_wsgi >> >> sudo apt-get remove libapache2-mod-wsgi >> >> # install the new 4.x wsgi-py27.so into the apache2 modules directory >> >> sudo mod_wsgi-express install-module >> >> sudo vi wsgi-py27.load >> >> And update that with the information that was sent to stdout by the >> previous command. >> >> And finally, >> >> sudo /etc/init.d/apache2 start >> >> ----------- >> Works great. >> >> >> On Mon, Oct 26, 2015 at 4:14 PM, Graham Dumpleton < >> [email protected]> wrote: >> >>> Have you looked through the online documentation, including: >>> >>> https://code.google.com/p/modwsgi/wiki/InstallationInstructions >>> >>> So in short, uninstall your existing mod_wsgi, then follow the >>> instructions there for building and installing from source code. >>> >>> If you were previously using system mod_wsgi packages, then you will >>> need to add to the Apache configuration the base configuration that loads >>> the mod_wsgi module as previously the configuration for that would have >>> been part of the installed system package. >>> >>> In most cases any other existing configuration should work the same. >>> >>> The alternative to using the old configure/make/make install method is >>> to use mod_wsgi-express but first pip installing it and then running: >>> >>> sudo mod_wsgi-express install-module >>> >>> That will copy the compiled module into the Apache modules directory, >>> then edit Apache configuration to load module. The install-module command >>> will give you the lines you need to add to the Apache configuration file. >>> >>> So have a look through that and when get to a specific problem let us >>> know. >>> >>> Graham >>> >>> On 27 Oct 2015, at 10:08 am, Mitch Sundt <[email protected]> >>> wrote: >>> >>> I have an existing Apache2 deployment of mod-wsgi 3.4.x on Ubuntu >>> >>> I'd simply like to upgrade that to use the latest mod-wsgi 4.x >>> >>> I cannot find any documentation on how to do that (i.e., not use >>> mod_wsgi-express). >>> >>> If I use: >>> >>> pip install mod_wsgi >>> >>> Where is the mod_wsgi.so placed? >>> >>> And can I then update the mods-available/wsgi.load file to point to that >>> location and have everything work? >>> >>> I also could not find find any migration documentation. >>> >>> What changes are required between the 3.x and 4.x versions? >>> >>> >>> >>> >>> >>> >>> -- >>> 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 [email protected]. >>> To post to this group, send email to [email protected]. >>> Visit this group at http://groups.google.com/group/modwsgi. >>> For more options, visit https://groups.google.com/d/optout. >>> >>> >>> >>> -- >>> 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 [email protected]. >>> To post to this group, send email to [email protected]. >>> Visit this group at http://groups.google.com/group/modwsgi. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> Mitch Sundt >> Software Engineer >> University of Washington >> [email protected] >> > > > > -- > Mitch Sundt > Software Engineer > University of Washington > [email protected] > > -- > 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 [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/modwsgi. > For more options, visit https://groups.google.com/d/optout. > > > -- > 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 [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/modwsgi. > For more options, visit https://groups.google.com/d/optout. > -- Mitch Sundt Software Engineer University of Washington [email protected] -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/modwsgi. For more options, visit https://groups.google.com/d/optout.
