no.no.no.no.no.no. use services, and separate ones. If you're on ubuntu writing something for upstart is utterly easy.
On Monday, September 2, 2013 1:51:49 PM UTC+2, lbd wrote: > > Hi guys, I have my prod deployment of Ubuntu running nginx and in turn > web2py. Also thanks to Niphlod I have all HTTP req's rewritten to https!!!! > I have an rq implementation in our code and would like to call web2py-rq.py > or run sudo rqworker on the box. In my pre prod environment (no nginx) I > just add it to the web2py startup scripts so no problem. > > My question is where is the best place to do this when running from nginx? > I could run it as a separate process entirely, but would really prefer it > if it was started by the same script that nginx uses to start web2py OR > should I have it as a web2py "cron" job? Either way when nginx starts > web2py an rqworker needs to be started. > > What is cnsidered "best practice" > > thanks > -- --- 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.
