Deployment Issues (Apache & mod_wsgi)

MediaDrop Community » General Discussion & Feedback

Deployment Issues (Apache & mod_wsgi)

7 posts Started 11 years ago by nbruzzi Latest reply from Felix Schwarz

nbruzzi
Member
Posted 11 years ago

With no knowledge of what I am actually doing - (I am a complete beginner when it comes to anything of this nature) - I have MediaCore up and running on a VPS (CENTOS 6.2 i686). I am having issues with deployment though. As stated in "Note 3" from the instructions here, I have added a VirtualHost include with the additional lines needed, changed to meet my installation of course.

Currently, I still receive a 404.... what might be the problem? Apparently with my lack of any foundational knowledge in anything web related there is something I am missing! :)

Help would be greatly appreciated!
Felix Schwarz
MediaDrop developer
Posted 11 years ago

Hi there,

Which URL use? The standard deployment from the docs uses http://yourdomain/my_media (you can change that easily though).

Also check that SElinux is not in enforcing mode (run the 'getenforce' command) and have a look at your Apache/vhost error log.
nbruzzi
Member
Posted 11 years ago

-bash: getenforce: command not found

Also, instead of "my_media", I used "watch".
And I left my MC install directory as "mediacore_install".

This is my VirtualHost include:

WSGIDaemonProcess mcore \
threads=10 \
display-name=%{GROUP} \
python-path=/mediacore_env/lib/python2.5/site-packages \
python-eggs=/mediacore_install/data/python-egg-cache

WSGIProcessGroup mcore

WSGIScriptAlias /watch /mediacore_install/deployment-scripts/mod_wsgi/mediacore.wsgi

<Location "/watch">
Allow from all
</Location>

<Directory /mediacore_install/deployment-scripts/mod_wsgi>
Order allow,deny
Allow from all
</Directory>

AliasMatch /watch/images/(media|podcasts)(.*) /mediacore_install/data/images/$1$2

AliasMatch /watch/(admin/)?(images|scripts|styles)(.*) /mediacore_install/mediacore/public/$1$2$3

Alias /watch/appearance /mediacore_install/data/appearance

<Directory /mediacore_install/mediacore/public/*>
Order allow,deny
Allow from all
Options -Indexes
</Directory>

Also, I am running Wordpress multisite. My current .htaccess file looks like this:

RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]

# uploaded files
RewriteRule ^([_0-9a-zA-Z-]+/)?files/(.+) wp-includes/ms-files.php?file=$2 [L]

# add a trailing slash to /wp-admin
RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]

RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule ^[_0-9a-zA-Z-]+/(wp-(content|admin|includes).*) $1 [L]
RewriteRule ^[_0-9a-zA-Z-]+/(.*\.php)$ $1 [L]
RewriteRule . index.php [L]
Felix Schwarz
MediaDrop developer
Posted 11 years ago

Very likely you have to modify your .htaccess so that MediaCore requests are not forwarded to WordPress' index.php. Try renaming your .htaccess and check if MediaCore works (if it does, the issue is within the .htaccess).

Probably you have to add a RewriteCond here:
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
nbruzzi
Member
Posted 11 years ago

Hi Felix,

Unfortunately, as I remove/rename the .htaccess file, I still receive a 404. It seems as though, that the problem is not getting access to MediaCore, but actually deploying it. It runs fine through the built in paster web server. Say I run "paster serve --reload deployment.ini", I can then check out my installation at "http://my-ip:8080"... But as I read here:

MediaCore CE is WSGI-based so there are many possible ways to deploy it. The built in Paste server does a great job for development, but you may want to run MediaCore CE from a more performant web server.

I have mod_wsgi installed, and as I previously mentioned above, I have already created a VirtualHost include. I seem to be one step from completion!

Thank you again.
nbruzzi
Member
Posted 11 years ago

Do the two need to see each other? Does something need to be "recognized"? Whether that's apache + mod_wsgi. or apache + the VH include...
Felix Schwarz
MediaDrop developer
Posted 11 years ago

Usually the problem is either in your Apache config or user permissions (the Apache user may not be able to access /mediacore_install).

> Do the two need to see each other? Does something need to be "recognized"? Whether that's apache + mod_wsgi. or apache + the VH include...

I'm not sure I understood you completely.

Basically mod_wsgi is an Apache module and needs to be configured in a virtualhost context. If you installed mod_wsgi through your distribution, I assume it'll be loaded by Apache (otherwise you'd get an error when you try to use mod_wsgi options like "WSGIDaemonProcess").

Did you check that your "vhost include" actually has any effect? Can you try configuring something completely independent of MediaCore (e.g. a simple alias for a static file) and try if that works?

Also please check your Apache logs if it says something there.

RSS feed for this topic

Reply

You must log in to post.

Community Forums

Deployment Issues (Apache & mod_wsgi)

Reply