schacki

Thinking about it, it absolutely makes sense to implement this kind of feature in fabric. But following above mentioned issues, it is not clear to me, when and if this...

@sebastien on the one hand, you prefer "sudo("some admin-related command")" over "with mode_sudo(): run("some admin-related command")", but at the same time you prefere "mode_sudo() instead of run in cuisine's core...

great discussion so far, so what is the bottom line? and i am not sarcarstic but really not sure :-) i think we agree on the issue, but not sure...

@madkinder: - getent, groups ==> maybe please put that into a separate thread - optional user argument to mode_sudo() defaulting to 'root' ==> great idea, and the same for mode_user()...

following this: http://docs.fabfile.org/en/1.3.4/usage/env.html#user, we could utilize for user argument of mode_user() could you explain the stack of modes in more detail please, and what would be the advantage?

to be consistent with fabric approach, should the mode_xxx() not wrap the fabric settings decorator. from my understanding, this is EXACTLY what we want.

regarding " proper user\* and group\* implementation", I would not recommend myself, my command line knowledge is limited (thats why I loave cuisine :-) ). I am happy to remove...

@fsw0422 : I think form data can be submitted via post or put requests, or am I wrong? my problem are files, which cannot simply be added to the db.json,...

Hi all, I am one of the guys who needs - or would like to have - role based object permissions. I understand from this discussion that for very good...

I would make any non-default checker classes not part of django-guardign but of the "other" app - so it is the job of the other app to the non-default checker...