Thank you for your help Graham. I [SOLVED] the problem by moving to slicehost :)
-Thadeus On Sat, Oct 24, 2009 at 3:48 AM, Graham Dumpleton < graham.dumple...@gmail.com> wrote: > > The other possibility of why you are having problems is that you have > conflicting VirtualHost definitions due to duplicate use of ServerName > for port 80 or overlapping ServerAlias pattern. End result being that > the other VirtualHost, which would precede this one in configuration > would be used and the mod_wsgi directives in later VirtualHost, as > well as AliasMatch would be ignored. > > Graham > > On Oct 24, 7:22 pm, Graham Dumpleton <graham.dumple...@gmail.com> > wrote: > > On Oct 24, 2:43 pm, Thadeus Burgess <thade...@thadeusb.com> wrote: > > > > > The paths are simlinked. > > > > You do realise that Apache treats symlinks as special and will not > > honour the target of a symlink as far as permissions access unless > > certain additional directives are supplied. > > > > So, use same physical path for both to ensure that you aren't getting > > tripped up by this security feature of Apache. > > > > > Also, the site does not work if WSGI declarations are in <VirtualHost> > > > > That doesn't change the fact that in a properly configured system they > > will work inside of VirtualHost and that is the preferred place if you > > are going to doing virtual site hosting. > > > > Graham > > > > > > > > > Remember, I am running on CentOS 5 not Ubuntu, debian, arch, or > slack... and > > > I have PLESK to deal with. > > > > > If I were running on ubuntu, I wouldn't even be asking any questions, > > > because it works perfectly on my home ubuntu server. > > > > > -Thadeus > > > > > On Fri, Oct 23, 2009 at 9:17 PM, Graham Dumpleton < > > > > > graham.dumple...@gmail.com> wrote: > > > > > > On Oct 24, 3:43 am, Thadeus Burgess <thade...@thadeusb.com> wrote: > > > > > So basically, from what I gather looking over what I have, the only > thing > > > > I > > > > > have wrong with my configuration is setting PythonHome and > SocketPrefix. > > > > > > > when I place the WSGIDaemon and WSGIProcessGroup and > WSGIScriptAlias in > > > > the > > > > > VirtualHost in httpd.conf, the site displays a directory listing of > > > > > /var/www/vhosts/domain/httpdocs > > > > > > > No error messages. > > > > > > > When I place the three WSGI declarations in the vhosts.conf file, > it > > > > > displays web2py. > > > > > > > Also, when the <Directory etcetc.> is in the httpd.conf instead of > > > > vhosts, > > > > > this happens...http://domain.com/welcome/static-> invalid > requesthttp:// > > > > domain.com/welcome/static/-> displays the /init/ application???? > > > >http://domain.com/welcome/static/base.css-> displays the base.css > from > > > > > welcome app. > > > > > > > Here is the updated scripts from the book. > > > > > > >http://pastebin.com/m113cd4de > > > > > > No it isn't because: > > > > > > WSGIDaemonProcess web2py user=apache group=apache display-name=% > > > > {GROUP} > > > > WSGIProcessGroup web2py > > > > WSGIScriptAlias / /opt/web2py/wsgihandler.py > > > > > > is meant to be inside of the VirtualHost along with the Directory > > > > directives which allow access to that location. > > > > > > The path doesn't even match as you have '/opt/web2py-devel' in one > > > > place and '/opt/web2py' in another. They should be the same. > > > > > > Graham > > > > > > > Also, here is the script I was using that worked, and > > > > > domain.com/welcome/static/ displayed a directory listing of the > static > > > > > directory. > > > > > > >http://pastebin.com/m4079cc37 > > > > > > > How would I set SSL up as well, with my config? I tried the below, > how > > > > the > > > > > whole site 503's but nothing gets written to error_log or my wsgi > error > > > > log > > > > > > >http://pastebin.com/mf9ed059 > > > > > > > Thanks. > > > > > > > -Thadeus > > > > > > > On Thu, Oct 22, 2009 at 7:42 PM, Thadeus Burgess < > thade...@thadeusb.com > > > > >wrote: > > > > > > > > Will do. I had used the 2nd edition, I will give it another shot > and > > > > let > > > > > > you know. > > > > > > > > I am probably also fighting with all of the VirtualHosts that > have been > > > > > > created through Plesk. Mainly the SSL stuff. > > > > > > > > Still confused as to whywww.site.comisdifferentfrom site.com. > > > > > > > > I can post more details tomorrow morning. > > > > > > > > Thanks > > > > > > > > -Thadeus > > > > > > > > On Thu, Oct 22, 2009 at 7:09 PM, Graham Dumpleton < > > > > > > graham.dumple...@gmail.com> wrote: > > > > > > > >> On Oct 23, 9:12 am, Thadeus Burgess <thade...@thadeusb.com> > wrote: > > > > > >> > The configuration from the book did not work for me. Using > centos5 > > > > on > > > > > >> Media > > > > > >> > temple's servers. with Plesk. > > > > > > > >> How did it not work? Without knowing the error messages you got > in > > > > > >> browser and Apache error logs, one can only guess why it didn't > work > > > > > >> for you. > > > > > > > >> Also ensure you are using 2nd edition of book and not the 1st > edition > > > > > >> as first edition instructions are very wrong and will not work. > > > > > > > >> > At the bottom of this message are links to how I configured > web2py > > > > on > > > > > >> > centos5. Not exact, I had to combine them with some in the > book as > > > > well. > > > > > > > >> > Here is a link to my config files... httpd.conf and vhost.conf > > > > > > > >> >http://pastebin.com/m243e0664 > > > > > > > >> With some mistakes as mentioned below. > > > > > > > >> > With this config, apache does serve the static files, without > a > > > > > >> directory > > > > > >> > listing, perfect. > > > > > > > >> > Though, only www. domain works, non-www will just direct to a > blank > > > > > >> page, > > > > > >> > which I can't locate where it is coming from. > > > > > > > >> > Right now I am just wanting a basic configuation, that works > with > > > > SSL > > > > > >> (my > > > > > >> > certificate is only for non-www version of the domain =/) In > any > > > > case, > > > > > >> it > > > > > >> > would at least be nice to redirect it to the correct location. > > > > > > > >> > Is this a VirtualHost problem in apache, or a DNS problem, or > a > > > > Plesk > > > > > >> issue? > > > > > >> > I'm at a loss on where to look. > > > > > > > >> >http://webmanufactory.blogspot.com/2009_06_01_archive.html > > > > > > > >> This page is misleading. The mod_wsgi stuff is meant to be > inside of > > > > > >> the VirtualHost, not outside. One shouldn't use 'processes=1' as > that > > > > > >> page says, not that you have. > > > > > > > >> >http://www.web2py.com/AlterEgo/default/show/240 > > > > > > > >> This page also has wrong information, you shouldn't be setting > > > > > >> WSGIPythonHome. > > > > > > > http://objectmix.com/python/342557-re-apache-mod_wsgi-daemon-mode.html > > > > > > > >> It is not recommended to use /tmp as location of sockets for > mod_wsgi > > > > > >> daemon mode. If you need to override default, you should use > proper > > > > > >> Apache run directory. In Centos use: > > > > > > > >> WSGISocketPrefix run/wsgi > > > > > > > >> See: > > > > > > > >> http://code.google.com/p/modwsgi/wiki/ConfigurationIssues > > > > > > > >> I would very much recommend going back to what 2nd edition of > web2py > > > > > >> books says to use, with only addition perhaps being correct > > > > > >> WSGISocketPrefix override required on Centos. > > > > > > > >> Then post error messages and better description of what didn't > work > > > > > >> along with configuration you are then using at that point. > > > > > > > >> Graham > > > > > > > >> > -Thadeus > > > > > > > >> > On Thu, Oct 22, 2009 at 4:39 PM, Graham Dumpleton < > > > > > > > >> > graham.dumple...@gmail.com> wrote: > > > > > >> > > at said, above looks correct in itself, but if you have gone > and > > > > > >> > > made other changes to the configuration example from web2py > book, > > > > then > > > > > >> > > you could have inadvertently caused it all to not work. So, > > > > posting > > > > > >> > > full configuration related to web2py hosting would be a good > ide > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
