15049 0 false 2008-07-17T00:52:23-04:00 26398 13708 21 support-for-non-admin-users-roles 1 10532 new model plugins users 2008-07-20T09:12:57-04:00 887 Alexander Flatter Daniel Bond Michael Leung http://feather.lighthouseapp.com/projects/10532/tickets/21 0.5 Feather owners might want to require users to login before writing a comment, or doing other cool stuff. Feather has a User-model, and a authentication-system that works great, so why reinvent the wheel? This could help creating plugins like OpenID provider/consumer, and other goodies. A approach is to implement a "role"-field to the User-model, and create some new methods and checks, for separating admins and users. There would have to be in place proper checks, so only admin can modify Admin-related functions, and some plugins might require modification. Users should perhaps have some kind of User-dashboard, which plugins could extend. Anyway, I forked the Feather-project on Github, and created a working concept of my thoughts: http://github.com/bond/feather/commit/6ce3a667d8add88cca0457300dbbcf3e13be29c5 Feather owners might want to require users to login before writing a comment, or doing other cool stuff. Feather has a User-model, and a authentication-system that works great, so why reinvent the wheel? This could help creating plugins like OpenID provider/consumer, and other goodies. A approach is to implement a "role"-field to the User-model, and create some new methods and checks, for separating admins and users. There would have to be in place proper checks, so only admin can modify Admin-related functions, and some plugins might require modification. Users should perhaps have some kind of User-dashboard, which plugins could extend. Anyway, I forked the Feather-project on Github, and created a working concept of my thoughts: http://github.com/bond/feather/commit/6ce3a667d8add88cca0457300dbbcf3e13be29c5 <div><p> Feather owners might want to require users to login before writing a comment, or doing other cool stuff. Feather has a User-model, and a authentication-system that works great, so why reinvent the wheel? </p><p> This could help creating plugins like OpenID provider/consumer, and other goodies. </p><p> A approach is to implement a "role"-field to the User-model, and create some new methods and checks, for separating admins and users. </p><p> There would have to be in place proper checks, so only admin can modify Admin-related functions, and some plugins might require modification. Users should perhaps have some kind of User-dashboard, which plugins could extend. </p><p> Anyway, I forked the Feather-project on Github, and created a working concept of my thoughts: </p><p> <a href="http://github.com/bond/feather/commit/6ce3a667d8add88cca0457300dbbcf3e13be29c5">http://github.com/bond/feather/c...</a> </p></div> 0 Feather owners might want to require users to login before writing a comment, or doing other cool stuff. Feather has a User-model, and a authentication-system that works great, so why reinvent the wheel? This could help creating plugins like OpenID provider/consumer, and other goodies. A approach is to implement a "role"-field to the User-model, and create some new methods and checks, for separating admins and users. There would have to be in place proper checks, so only admin can modify Admin-related functions, and some plugins might require modification. Users should perhaps have some kind of User-dashboard, which plugins could extend. Anyway, I forked the Feather-project on Github, and created a working concept of my thoughts: http://github.com/bond/feather/commit/6ce3a667d8add88cca0457300dbbcf3e13be29c5 <div><p> Feather owners might want to require users to login before writing a comment, or doing other cool stuff. Feather has a User-model, and a authentication-system that works great, so why reinvent the wheel? </p><p> This could help creating plugins like OpenID provider/consumer, and other goodies. </p><p> A approach is to implement a "role"-field to the User-model, and create some new methods and checks, for separating admins and users. </p><p> There would have to be in place proper checks, so only admin can modify Admin-related functions, and some plugins might require modification. Users should perhaps have some kind of User-dashboard, which plugins could extend. </p><p> Anyway, I forked the Feather-project on Github, and created a working concept of my thoughts: </p><p> <a href="http://github.com/bond/feather/commit/6ce3a667d8add88cca0457300dbbcf3e13be29c5">http://github.com/bond/feather/c...</a> </p></div> false 2008-07-17T00:52:23-04:00 26398 --- {} 21 support-for-non-admin-users-roles 0 10532 new model plugins users 2008-07-17T00:52:23-04:00 26398 Daniel Bond Daniel Bond http://feather.lighthouseapp.com/projects/10532/tickets/21 0 Hi there, Your fork seems to be empty? <div><p> Hi there, </p><p> Your fork seems to be empty? </p></div> false 2008-07-17T19:25:09-04:00 26398 --- {} 21 support-for-non-admin-users-roles 0 10532 new model plugins users 2008-07-17T19:25:09-04:00 887 Alexander Flatter Daniel Bond http://feather.lighthouseapp.com/projects/10532/tickets/21 0 Sorry about that, something was wrong with github, so I deleted/recreated the repo and pushed my changes to it. <div><p> Sorry about that, something was wrong with github, so I deleted/recreated the repo and pushed my changes to it. </p></div> false 2008-07-17T21:19:43-04:00 26398 --- {} 21 support-for-non-admin-users-roles 0 10532 new model plugins users 2008-07-17T21:19:43-04:00 26398 Daniel Bond Daniel Bond http://feather.lighthouseapp.com/projects/10532/tickets/21 15049 0 Looks good, I like it. More fine-grained permission checks could be implemented later. Michael, what do you think? <div><p> Looks good, I like it. More fine-grained permission checks could be implemented later. </p><p> Michael, what do you think? </p></div> false 2008-07-18T06:35:13-04:00 26398 --- :assigned_user: 21 support-for-non-admin-users-roles 0 10532 new model plugins users 2008-07-18T06:35:13-04:00 887 Alexander Flatter Daniel Bond Michael Leung http://feather.lighthouseapp.com/projects/10532/tickets/21 15049 0 I think this is something we should look to wrap up and stabilize as part of 0.5, I like it and think it'll be very useful. We are continuing to discuss this in IRC, and we'll roll it in as and when Daniel thinks he has something that is ready to go. Incidentally, I've created "edge" branches in both core and plugins, so we should probably try to sync up this code with that, as this will probably be best running off of the merb-auth slice that TheWordNerd implemented. That currently only runs on Merb edge (until 0.9.4 hits which includes merb-slices). <div><p> I think this is something we should look to wrap up and stabilize as part of 0.5, I like it and think it'll be very useful. We are continuing to discuss this in IRC, and we'll roll it in as and when Daniel thinks he has something that is ready to go. </p><p> Incidentally, I've created "edge" branches in both core and plugins, so we should probably try to sync up this code with that, as this will probably be best running off of the merb-auth slice that TheWordNerd implemented. That currently only runs on Merb edge (until 0.9.4 hits which includes merb-slices). </p></div> false 2008-07-18T17:37:07-04:00 26398 --- :milestone: 13708 21 support-for-non-admin-users-roles 0 10532 new model plugins users 2008-07-18T17:37:07-04:00 18455 Elliott Draper Daniel Bond Michael Leung http://feather.lighthouseapp.com/projects/10532/tickets/21 0.5 15049 0 I created a branch of your "edge" branch, called "edge-db", which I've based the same implementation on: http://github.com/bond/feather/commit/0339af9ebe48627e950962ed6af1fded70f76bd4 Since merb-auth is a seperate project under feather, I've forked it too, and sent a pull-request: http://github.com/bond/merb-auth/commit/22381302ea7b1ca783f7c6509ee2024af0782f80 We still need to create some kind of dashboard for the users to set properties and hook plugin-stuff in, but we'll discuss that further if the merb-auth stuff goes through. <div><p> I created a branch of your "edge" branch, called "edge-db", which I've based the same implementation on: <a href="http://github.com/bond/feather/commit/0339af9ebe48627e950962ed6af1fded70f76bd4">http://github.com/bond/feather/c...</a> </p><p> Since merb-auth is a seperate project under feather, I've forked it too, and sent a pull-request: <a href="http://github.com/bond/merb-auth/commit/22381302ea7b1ca783f7c6509ee2024af0782f80">http://github.com/bond/merb-auth...</a> </p><p> We still need to create some kind of dashboard for the users to set properties and hook plugin-stuff in, but we'll discuss that further if the merb-auth stuff goes through. </p></div> false 2008-07-19T22:24:52-04:00 26398 --- {} 13708 21 support-for-non-admin-users-roles 0 10532 new model plugins users 2008-07-19T22:24:52-04:00 26398 Daniel Bond Daniel Bond Michael Leung http://feather.lighthouseapp.com/projects/10532/tickets/21 0.5 15049 0 AFAIK slices are thought to be extended in their host application, so that there is no need to modify merb-auth. merb-auth is a gem that you can install. You can then override gem files in your app-root/app/slices directory. <div><p> AFAIK slices are thought to be extended in their host application, so that there is no need to modify merb-auth. </p><p> merb-auth is a gem that you can install. You can then override gem files in your app-root/app/slices directory. </p></div> false 2008-07-20T09:12:57-04:00 26398 --- {} 13708 21 support-for-non-admin-users-roles 0 10532 new model plugins users 2008-07-20T09:12:57-04:00 887 Alexander Flatter Daniel Bond Michael Leung http://feather.lighthouseapp.com/projects/10532/tickets/21 0.5