Talk:Deployment: Difference between revisions

From GNU MediaGoblin Wiki
Jump to navigation Jump to search
No edit summary
 
Line 11: Line 11:


I couldn't make it work without adding something like this:
I couldn't make it work without adding something like this:



<Directory "/data/mediagoblin/mediagoblin/">
<Directory "/data/mediagoblin/mediagoblin/">
Line 19: Line 20:
</Files>
</Files>
</Directory>
</Directory>



Without granting access in apache, it wont be able to access the wsgi.py script. Even if the conf above works for me, I dont think it is really the best way to do it (I'm far from being an apache expert :D)
Without granting access in apache, it wont be able to access the wsgi.py script. Even if the conf above works for me, I dont think it is really the best way to do it (I'm far from being an apache expert :D)

Latest revision as of 10:41, 31 July 2014

Deployment#Running_MediaGoblin.27s_web_server_and_Celery_separately

./lazyserver.sh is all good and well for debugging, but probably not for deployments. Instead, you should probably run

It seems that something's missing…
Joar 16:19, 21 September 2011 (EDT)

mod-wsgi apache conf

I couldn't make it work without adding something like this:


<Directory "/data/mediagoblin/mediagoblin/">

 <Files "wsgi.py">
   Order allow,deny
   Allow from all
   Require all granted
 </Files>

</Directory>


Without granting access in apache, it wont be able to access the wsgi.py script. Even if the conf above works for me, I dont think it is really the best way to do it (I'm far from being an apache expert :D) I think "Allow from all" and "Require all granted" are not supposed to be combined that way, but I havent been able to make it work with only one of them..