I went ahead an wrote up a recipe showing it but currently (thanks to some serious sinus congestion) can't think of a good example for where to use it. In fact, think I originally thought more of being able to have a whole class of model have group permissions. Hmm...
On Aug 10, 2:30 pm, Owen Dall <[email protected]> wrote: > I like it... > > - Owen > > On Tue, Aug 10, 2010 at 4:01 PM, kevinpfromnm <[email protected]>wrote: > > > > > Well, what I'm trying to do is make a generally useful unix style > > permissions module. i.e. each model with this module will have an > > owner, a group and ability to set view/update/destroy permissions > > based on group/everyone. > > >http://gist.github.com/517863 > > > I originally thought to include owner permissions but found it doesn't > > make a lot of sense for owners to not be able to view or modify their > > own stuff on a selective basis. I added in early exit hooks (probably > > is a better way of doing this) so that it's possible to do selective > > permissions changes without having to override the whole basic > > permission method. > > > Not shown in this is a basic group model with join table so users can > > have many groups (and maybe a default group). > > > Obviously not needed in a lot of places, but seems like it could be > > used a few cases and might be an example for one way to setup a > > permissions system. Any thoughts or improvements? > > > On Aug 10, 5:38 am, Owen Dall <[email protected]> wrote: > > > Yes, an example would be very useful. > > > > On Mon, Aug 9, 2010 at 8:37 PM, Skott Klebe <[email protected]> wrote: > > > > I'd love to see how that works out - sounds like some stuff I was > > > > trying a while back. > > > > > SK > > > > > On Mon, Aug 9, 2010 at 5:48 PM, kevinpfromnm <[email protected]> > > > > wrote: > > > > > I know odd question, but was thinking of extracting out some model > > > > > functionality into a classy_module and it would be nice to be able to > > > > > add fields from the module. > > > > > > -- > > > > > You received this message because you are subscribed to the Google > > Groups > > > > "Hobo Users" group. > > > > > To post to this group, send email to [email protected]. > > > > > To unsubscribe from this group, send email to > > > > [email protected]<hobousers%[email protected]> > > <hobousers%[email protected]<hobousers%[email protected]> > > > > > . > > > > > For more options, visit this group at > > > >http://groups.google.com/group/hobousers?hl=en. > > > > > -- > > > > Skott Klebe > > > > [email protected] > > > > > -- > > > > You received this message because you are subscribed to the Google > > Groups > > > > "Hobo Users" group. > > > > To post to this group, send email to [email protected]. > > > > To unsubscribe from this group, send email to > > > > [email protected]<hobousers%[email protected]> > > <hobousers%[email protected]<hobousers%[email protected]> > > > > > . > > > > For more options, visit this group at > > > >http://groups.google.com/group/hobousers?hl=en. > > > > -- > > > - Owen > > > > Owen Dall, Chief Systems Architect > > > Barquin International > > > Cell: 410-991-0811 > > > -- > > You received this message because you are subscribed to the Google Groups > > "Hobo Users" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]<hobousers%[email protected]> > > . > > For more options, visit this group at > >http://groups.google.com/group/hobousers?hl=en. > > -- > - Owen > > Owen Dall, Chief Systems Architect > Barquin International > Cell: 410-991-0811 -- You received this message because you are subscribed to the Google Groups "Hobo Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/hobousers?hl=en.
