THANK YOU VERY MUCH!!!

I knew I was missing something.  I now understand my error: by not being in 
daemon mode, my site would not load without changing the user/group.  This 
was also forcing me to run a "sudo brew services restart -k apache2" every 
time the mac restarted in order for the site to load.

Using mod_wsgi in daemon mode was the key to life.  My site is now work 
flawlessly.

Thanks again

Erick

On Tuesday, January 15, 2019 at 3:21:28 PM UTC-5, Graham Dumpleton wrote:
>
>
>
> On 16 Jan 2019, at 6:26 am, Erick L. <[email protected] <javascript:>> 
> wrote:
>
> Graham,
>
> First off I would like to thank you for your prompt response.  
>
> Following your guidelines, I have been successful.
>
> I got it to work  using "pip3 install mod_wsgi --no-cache-dir" after the 
> Apache installation through HomeBrew.
>
> Also would like to note that after adding the module to httpd.conf I 
> needed to change "User and Group" in the file to [CurrentUser] and "staff" 
> respectively. (Defaults to "_www" for both).
>
>
> You shouldn't really ever change those, even if the issue is that the 
> Apache user cannot read files/directories because of permissions.
>
> You are better off using mod_wsgi daemon mode and only changing user/group 
> for that mod_wsgi daemon process group to match yours. If done that way, 
> the only directory/file that needs to be accessible to Apache user is that 
> for the WSGI script file, which you can co-locate with the Apache 
> installation outside of your home directory.
>
> What was the specific reason you felt you needed to change it?
>
> FWIW, use of mod_wsgi daemon mode is the recommended configuration either 
> way.
>
> Graham
>
>
> Thanks again Graham it was much appreciated. :) 
>
> Erick,
>
>
> On Friday, January 11, 2019 at 2:46:32 PM UTC-5, Graham Dumpleton wrote:
>>
>> You can't use Apache httpd server from Apple on Mojave as you need the 
>> Apache modules to be signed by a registered developer.
>>
>> What exactly have you tried, ie. what commands are you running to install 
>> things? Do you have to use system Apache, or even a self configured Apache, 
>> can you use mod_wsgi-express start-server?
>>
>> The choices are:
>>
>> 1. Use Apache from HomeBrew.
>>
>> 2. Install the mod_wsgi-httpd package first if only want mod-wsgi-express 
>> start-server.
>>
>> Ensure that you set APXS=/usr/local/sbin/apxs when building with HomeBrew 
>> if that directory isn't in PATH before system directories.
>>
>> Very important if using configure/make/make install method with HomeBrew, 
>> start with fresh source code, or do a make distclean before running 
>> configure, if you already tried to build source code for Apple version of 
>> Apache.
>>
>> Also, if you have used pip install method for mod_wsgi, ensure you use 
>> --no-cache-dir to ignored cached build if previously attempted for Apple 
>> version of Apache.
>>
>> Graham
>>
>> On 12 Jan 2019, at 1:05 am, Erick L. <[email protected]> wrote:
>>
>> I am setting up a new Mac server running Mojave 10.14.2 to run with 
>> django and which utilizes mod_wsgi for Apache.
>>
>>
>> When adding the configuration to load the mod_wsgi module, Apple does not 
>> allow for third party modules with their Apache installation.
>>
>>
>> I have this working on a windows PC but need to put on the Mac server.
>>
>>
>> I have tried a few things as posted HERE 
>> <https://github.com/GrahamDumpleton/mod_wsgi/issues/357> but still can 
>> not get it to work.  
>>
>>
>> I have also tried a custom installation of httpd through homebrew and it 
>> does not work.
>>
>>
>> Error recieved: "not valid for use in process using Library Validation: 
>> mapped file has no cdhash, completely unsigned? Code has to be at least 
>> ad-hoc 
>> signed.\n\t/Users/yosifov/Sites/hello/venv/lib/python3.7/site-packages/mod_wsgi/server/
>> mod_wsgi-py37.cpython-37m-darwin.so: stat() failed with errno=22"
>>
>> -- 
>> 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 https://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] <javascript:>.
> To post to this group, send email to [email protected] <javascript:>
> .
> Visit this group at https://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 https://groups.google.com/group/modwsgi.
For more options, visit https://groups.google.com/d/optout.

Reply via email to