it's not how much users are there, but how many requests they'll generate (requests is more or less the number of pages visited). If 50 users will access e.g. one page every 5 seconds, if you app is "simple" there should be no problems. Note that most of the performance depends also if you're on Windows or on Unix (talking about where the default webserver will be executed).
PS: you don't need anything fancy as apache to make web2py "more capable": tell us what's your OS and we can come up with solutions. On Thursday, March 14, 2013 9:45:38 AM UTC+1, Sarbjit singh wrote: > > Hi, > > I have started learning web2py for web development in Python. Initially I > started with Django, but found on internet that web2py is easy to learn and > provides more features over django. However I have one basic question :- > > Can I use default web2py server in production. I want to build an database > based web app using web2py. Number of users that will access the site will > be less than 50 (Intranet site only). I don't want to configure apache for > it. So, I was wondering if web2py default server will solve this purpose. > > -Sarbjit > -- --- 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.
