As of v0.15.0.0, the deployment on webfaction correctly uses a separate Python virtualenv. The location of that virtualenv is encoded in the configuration file. In order for it to be used under Apache I activate that virtualenv at the start of the wsgi script. There ought to be a check that the configuration file used by wsgi is the same one as that used by the Django project's global settings.
WHO: @allynt
As of v0.15.0.0, the deployment on webfaction correctly uses a separate Python virtualenv. The location of that virtualenv is encoded in the configuration file. In order for it to be used under Apache I activate that virtualenv at the start of the wsgi script. There ought to be a check that the configuration file used by wsgi is the same one as that used by the Django project's global settings.