that is something I am going to need at the same time, I think I can manage that through the server itself.
thanks On Jan 26, 11:19 am, Massimo Di Pierro <[email protected]> wrote: > Rocket is very robust and fast. The only reason to use apache instead > in production are(were) Apache has many more configuration options, in > particular security options such as allow/deny clients and individual > urls. > > On Jan 26, 11:32 am, greenpoise <[email protected]> wrote: > > > > > I read on the Web2py Deployment recipes Chapter of the book that the > > webserver web2py runs in is should be avoided for production > > environments of high volume traffic. My setup is within the company > > (intranet) with limited access to other offices. I cant specify the > > volume of traffic it will receive but in terms of workstations > > accessing it, 20-30 maximum, no more than that. My questions are: > > > 1. Should I still avoid Rocket? > > 2. If not, is it just a matter of executing web2py as it is? > > > If is still not worth it, I will move on with another webserver. > > > Thanks > > > Dan
