It's a bit hidden in the deployment recipes page but as far as I know the easiest way to make your site go live using the built in server is this:
An easy way to setup a secure production environment on a server is to > first stop web2py and then remove all the parameters_*.py files from the > web2py installation folder. Then start web2py without a password. This will > completely disable admin and appadmin. > > nohup python web2py --nogui -p 8001 -i 127.0.0.1 -a '' & > > More details on how to access admin securely here: http://web2py.com/books/default/chapter/29/13/deployment-recipes#Securing-sessions-and-admin On Saturday, February 22, 2014 6:32:49 PM UTC, aslav wrote: > > Hi there, I'm new to programming, python and web2py. I have a question - > Can I use web2py build-in server insted of apache if I'm just running a > small ( really small ) website with couple of visits and file downloads per > day? > -- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
