there is no facility to queue a task (or any a piece of code) only at the first request consistently. This doesn't mean that it isn't possible, just that there's not any easy machinery to do so. on top of my head: - queue the task just before launching web2py - queue the task every once in a while (cron?) checking if it's already there - check in cache.ram for some "stopgap" value: if it isn't there, queue a task and then cache the "stopgap"
On Monday, November 16, 2015 at 10:19:09 PM UTC+1, noam cohen wrote: > > Where is the recommended location to add the queue_task() so it runs > exactly once when my app starts? > I thought about .../applications/my_app/__init__.py but it was called > TWICE (once by the web server and once by the scheduler, if I got it right) > > I could of course check if the task is already queue by querying the > database but it seems less elegant. > -- 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/d/optout.
