I thought that's what you intended. But as I'm the one who's obviously not understanding something very simple - like the example in the deployment recipe section - I'm the one waving the idiot banner and as such have had all powers of assumption revoked.
Anyway, I have enabled the site that utilizes the WGSI Directives. I'm able to navigate to the IP associated with the server and view the welcome page in all it's orange and bold text glory. One of the main differences to my config as to the examples is that Alias Directive line: "Alias / /home/web2py/applications/" In my config I have that commented out. As when I have it uncommented it doesn't allow WSGI to run. On Apr 7, 9:25 am, bsnipes <snipes.br...@gmail.com> wrote: > On Apr 7, 9:20 am, zxynax <zxy...@gmail.com> wrote: > > > a2enmod web2py returns "ERROR: Module web2py does not exist!" > > oops... I guess that should be a2ensite web2py... > > I'll power on my laptop that I was testing with and paste them > shortly. > > Brian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" 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 -~----------~----~----~----~------~----~------~--~---
