Concepts that come to mind are:
* role based authentication
* grouping controllers into name spaces [1]
* with_scope [2]
These might not be the best articles, but just to get you started:
[1] http://peat.wordpress.com/2006/06/30/watch-your-namespace/
[2] http://habtm.com/articles/2006/02/22/nested-with_scope
On 11/30/06, Szymek ---
<rails-mailing-list-ARtvInVfO7ksV2N9l4h3zg@public.gmane.org>
wrote:>
>
> Hi,
>
> I made few simple pages before using rails and I always created separate
> set of controllers for admin section and put them in a group. However,
> using this method, some actions were identical with actions for a
> ''normal'' user. So i was thinking about creating just a
single controller
> for both ''normal'' user and admin at the same time, where
some actions
> could be only accessed by admin and the content would be displayed
> differently depending on who''s actually logged in. However,
I''m not sure
> if putting all functionality into a single controller, won''t make
it all
> just more complicated (more code in a single controller etc.)
>
> Do you have any suggestions or maybe know a tutorial or a blog entry
> discussing this problem?
>
> --
> Posted via http://www.ruby-forum.com/.
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---