Sorry about that. I think the right approach was to have the python stubs
to invoke scheduled jobs, under models directory and the modules with
python functions, under modules directory. That way I need not worry about
a normal portal user attempting to invoke the scheduler jobs.
On Tuesday, January 21, 2014 9:33:55 PM UTC+5:30, Niphlod wrote:
>
> the wording is a little bit incorrect.
>
> You may prevent users queuing tasks, and that's pretty much all about what
> can you do with auth.has_membership.
>
> """
> python files being executed by other users
> """
> seems to point to the security of the server itself, that web2py can't
> really manage.
>
> Can you be clearer ?
>
> On Tuesday, January 21, 2014 10:22:04 AM UTC+1, Jayadevan M wrote:
>>
>> I wanted to set up the scheduler and execute a few jobs. To prevent the
>> python files being executed by other users, I have added a condition
>> auth.has_membership('scheduler') in the functions. How can I make the
>> scheduler start with a user who in in the scheduler group? Or I am going
>> down the wrong path?
>>
>
--
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 web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
