, at 8:16 AM, Tierprot B. <tierp...@gmail.com> wrote:
>
> Aha! Thanks! Addition of proper user and group options to
> WSGIDaemonProcess solved the ImportError! The last question i have might
> be not related to mod_wsgi directly, but still.
> I have a Flask app, purpose of which to
th to the python-path option as your snippet showed.
>
> Graham
>
> On 21 Aug 2016, at 11:41 PM, Tierprot B. <tierp...@gmail.com> wrote:
>
>
>> That is what WSGIScriptAlias is doing in giving it the path to the WSGI
>> script file. If you mean something different you
Thanks for the fast reply! I did what you`ve wrote and yay it worked! Now i
wondering how can i tell to mod_wsgi two things - a) that wsgi file itself
lies in /var/www/wsgi-scripts and b) that it should include python files
from outside directory, for example home/user/flask_stuff_files ?
--
>
>
> That is what WSGIScriptAlias is doing in giving it the path to the WSGI
> script file. If you mean something different you need to be clearer.
>
> b) that it should include python files from outside directory, for example
> home/user/flask_stuff_files ?
>
>
> If you are talking about
Good day, im trying to deploy a server on CentOs7 in combination
Flask+Apache 2.4+mod_wsgi 4.5.5. Mod_wsgi was compiled with python 3.5.2
and test-run from manual works fine. However when i tried to connect mine
app i failed so i reduced tests to only Apache+mod_wsgi stack and found
that
