Okay, I figured out what happened. During the "One step production deployment", *for some reason*, the wsgihandler.py file did NOT get copied to the web2py parent folder. Don't ask me why. (In my test VM, the wsgihandler.py file did get copied, in fact, moved. Go figure.)
Now, I'm finding that the Administrative Interface cannot locate the CSS for proper rendering. Any ideas? (Why is "One step production deployment" going so wrong???) On Saturday, 15 March 2014 07:57:59 UTC-4, horridohobbyist wrote: > > I'm trying to reinstall web2py on my Linux server. I'm trying to start > from a clean slate... > > First, I've updated my server to Ubuntu Server 12.04. I've restored the > original *httpd.conf* (empty file) and *sites-available/default* files > for Apache2. So, for all intents and purposes, web2py is gone from my > system. > > Then, I removed all things web2py from the */home/www-data* folder. So I > have a clean slate, right? > > Finally, I followed the "One step production deployment" recipe. So, the > thing should just work, right? > > Except, it doesn't. Visit http://67.213.70.250/welcome and you get > nothing, /welcome Not Found. > > Um, what's wrong? > > This worked just fine in my Linux VM, so I am puzzled. > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
