Re: [modwsgi] Wordpress & Flask sitewide implimentation

Graham, After you stated the expected behavior in this thread, I did spend the time to read through the Apache documentation on RewriteCond and RewriteRule (in particular the flags); however, even if I had read the Apache documentation and interpreted it correctly prior to following the post

Re: [modwsgi] Wordpress & Flask sitewide implimentation

The behaviour is dictated by: RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d This in combination says to rewrite it if the target is neither a file or a directory. Technically you could remove the second one for the directory (I think), and if

Re: [modwsgi] Wordpress & Flask sitewide implimentation

Graham, A gracious thank you for your help and all the effort you have put into mod_wsgi. Removing the zones subdirectory resulted in the launching of main.py and the site is now working as expected. While not in this space and predominantly in IC development, my organization and myself have

Re: [modwsgi] Wordpress & Flask sitewide implimentation

What is the 'zones' sub directory under the document root for? A request will only be redirected to use main.py in document root as handler if the URL path doesn't match either a directory or any file (not just .php files). So if you have a 'zones' sub directory, and use a URL with path of

Re: [modwsgi] Wordpress & Flask sitewide implimentation

Same result. If the browser is directed to http://thegacway.com/zones/ the same error is generated. Unfortunately, I don't believe I have a handle on the mechanisms / behaviors of this solution. My understanding was that if a directory under the root directory did not have a .php file in

Re: [modwsgi] Wordpress & Flask sitewide implimentation

If you are still using: RewriteRule ^(.*)$ /main.py/$1 [QSA,PT,L] the file 'main.py' must be in the document root directory for Apache, presumably next to 'index.php'. Try that first. Graham > On 12 Sep 2020, at 6:52 am, Gordon Charles wrote: > > Graham, > > I have not been successful

Re: [modwsgi] Wordpress & Flask sitewide implimentation

Graham, I have not been successful in launching a python application. My understanding is the configuration should launch the php handler if it finds a .php file in a directory and if not a .php file, but a ,py file exists it should launch that. The rules in the configuration file and the

Re: [modwsgi] Wordpress & Flask sitewide implimentation

Setting FollowSymLinks and SymLinksIfOwnerMatch worked. Thank you. I'm including the working .conf files for reference: Require all granted WSGIRestrictEmbedded On ServerName thegacway.com ServerAlias www.thegacway.com ServerAdmin webmaster@localhost

Re: [modwsgi] Wordpress & Flask sitewide implimentation

Is there is a reason why use of mod_rewrite is disabled by not setting FollowSymLinks and SymLinksIfOwnerMatch. Can only presume then that is due to that. > On 11 Sep 2020, at 1:29 pm, Gordon Charles wrote: > > Graham, > > I genuinely appreciate your help and patience; however, I believe we

Re: [modwsgi] Wordpress & Flask sitewide implimentation

Graham, I genuinely appreciate your help and patience; however, I believe we may be struggling to communicate. To be clear the .conf file I provided is the one, only and the complete contents of the .conf file. To be clear, yes I would like the site(s) to be under the same address/port and

Re: [modwsgi] Wordpress & Flask sitewide implimentation

You can't have two VirtualHosts for same port with same ServerName. Apache will always use the first matching one it finds when doing named based virtual hosting. If you want both sites to be under the same host name, the configuration for each must be combined under the one VirtualHost

Re: [modwsgi] Wordpress & Flask sitewide implimentation

Graham, No it is not different. My understanding having read your post Graham Dumpleton Post , was that when configured Apache would dynamically route requests to either the .php or through wsgi based upon the file

Re: [modwsgi] Wordpress & Flask sitewide implimentation

What is the ServerName/ServerAlias for the wordpress VirtualHost? It is different right? > On 11 Sep 2020, at 10:00 am, Gordon Charles wrote: > > Graham, > > Thanks for the quick reply. I am striving to work independently here. I've > made the modification, wordpress, is still not loading

Re: [modwsgi] Wordpress & Flask sitewide implimentation

Graham, Thanks for the quick reply. I am striving to work independently here. I've made the modification, wordpress, is still not loading and have the following in the error.log file: [Thu Sep 10 23:53:15.963956 2020] [mpm_prefork:notice] [pid 40224] AH00163: Apache/2.4.41 (Ubuntu)

Re: [modwsgi] Wordpress & Flask sitewide implimentation

Only WSGIRestrictEmbedded needs to be outside of the VirtualHost. Leave everything else you may have inside of the VirtualHost. > On 11 Sep 2020, at 8:17 am, Gordon Charles wrote: > > I've been trying to create a .conf file which would simultaneously support > Wordpress and Flask (I have some