ansaurus

Question

Running a PHP script inside a Python WSGI enviroment

Answer 1

+2 A:

Maybe read this thread, and port your PHP script to Python:

http://stackoverflow.com/questions/2104997/os-walk-python-xml-representation-of-a-directory-structure-recursion

AJ 2010-01-29 03:08:54

I've considered writing it into my django project, but it does not actually have an app of it's own. It's just running my CMS app imported from a shared source.I don't know how so serve up a python script to a URL other than through Django. I expected what I've done would work, if I could get it going it would be much simpler and would allow me to use the same script on Django and non-django sites.

Jake 2010-01-29 05:22:01

Answer 2

+1 A:

If you have not configured Apache so that it knows that .php files under the '/media' directory should be processed by PHP somehow, they will not be. So, the mod_wsgi configuration is fine, the problem is likely your PHP configuration.

How are you configuring PHP? Are you using mod_php, or PHP via fastcgi? How is Apache configured so that it knows to treat .php files as PHP and for what directories has that configuration been applied to?

Graham Dumpleton 2010-01-29 04:17:40

If I remove the vhost.conf file it works, but Django does not. So I think PHP is setup fine.

Jake 2010-01-29 05:23:03

PHP will work fine, but you have not configured Apache correctly (yet) in this case.

Ali A 2010-01-29 09:32:56

Apache must be setup to treat .php files as PHP because it does in the absence of Django. The problem seems to be that apache is not handling the file as usual, it's running it through mod_wsgi. See Ignacio's answer.

Jake 2010-01-29 10:05:40

Post the Directory block related to the media directory as followup in your question. You haven't gone and made the mistake that people do when they move from mod_python and put 'SetHandler None' in it have you. This will stop PHP from working. When using mod_wsgi, 'SetHandler None' should never be used.

Graham Dumpleton 2010-01-29 11:34:31

Thanks for the suggestion. A likely mistake, but not one I've made.

Jake 2010-02-12 22:01:31

Answer 3

+1 A:

The WSGIScriptAlias directive there swallows up URLs meant for Alias. Swap the order.

Ignacio Vazquez-Abrams 2010-01-29 04:24:13

Nope, still serving up the file without parsing it.Other files served under /media work with them in the original order, so I don't think it swallows.

Jake 2010-01-29 05:26:16

If at some point the Django project had been set up for serving static files then it would still be in the way with the original order. Do other PHP files on the server get handled properly?

Ignacio Vazquez-Abrams 2010-01-29 05:40:55

Good point. I have django setup files under /media when in debug mode for local dev. I've tested and found is in debug mode for some reason, I'll check my config. I also realised that I neglected to restart the server after reversing those 2 lines, restarting that causes a 500 error. I think I'm on the right track once I sort that out, so thanks. Will keep you posted when I get time to test it.

Jake 2010-01-29 10:00:37

OK, so even without the WSGIScriptAlias, only a normal Alias it still serves the file without parsing it. It is caused by the alias, with my file at ...httpdocs/media/test.php and an Alias /media2/ ...httpdocs/media/ it is served interpreted from domain.com/media/test.php and as raw code from domain.com/media2/test.php. Anyone know how to change this behavior?

Jake 2010-02-12 21:01:06

At this point try adding the following:`AddHandler php5-script .php``AddType text/html .php`

Ignacio Vazquez-Abrams 2010-02-12 21:04:23

That has stopped my browser thinking the file is a download. It's now displaying the php code rather than giving me the file. But it's still not interpreting it. :(

Jake 2010-02-12 21:53:55

Well then I am truly and rightly stumped...

Ignacio Vazquez-Abrams 2010-02-12 22:32:13

Thanks for your help, your original answer helped anyway. I'll setup some proper tests to see just what works and doesn't then ask another question.

Jake 2010-02-12 23:36:46

Answer 4

+1 A:

So it turns out the problem was two things, making it hard to find.

Thanks Ignacio Vazquez-Abrams, I had my lines the wrong way around.

Once that was solved, PHP would not serve my file because it was in a dir that was symlinked from outside the allowed path(s). I resolved this by turning off open_basedir restrictions for this vhost. My new vhost.conf is below.

<Directory /var/www/vhosts/<domain>/httpdocs>
    php_admin_flag engine on
    php_admin_value open_basedir none
</Directory>

Alias /media/ /var/www/vhosts/<domain>/httpdocs/media/

WSGIScriptAlias / /var/www/vhosts/<domain>/conf/django.wsgi

Jake 2010-02-13 04:27:40

Answer 5

A:

It's a bit more secure to specify your open_basedir paths, rather than disabling open_basedir entirely.

Instead of:

php_admin_value open_basedir none

Use:

php_admin_value open_basedir "/var/www/vhosts/domain.com/httpdocs/:/tmp/:/path/to/django/app/"

You can add as many paths as you want - just separate with colons.

Shar 2010-10-12 21:54:13

ansaurus

tags:

views:

answers:

Running a PHP script inside a Python WSGI enviroment

related questions