On Aug 4, 2009, at 2:18 PM, Klaus wrote:
> > That's not what I'm looking for. > I'm looking for a DRY solution. > At least the document model should not repeat. It's close. Just create a set of controllers/views for your admin stuff. I tend to put them into app/controllers/admin and app/views/ admin. Then this all gets password protected. I use the same models that the public facing website uses that live in app/models. This is DRY in the sense that (presumabely) what you are doing in the admin section is quite different than what the public can do. If you want to blend them all together you're free to do that too. All depends on what makes the most sense for your app. > On 4 Aug., 23:09, thumbrule <[email protected]> wrote: >> I guess a way to do this is to set up an admin area (by designating a >> folder called admin within your application) - then put th >> controllers, models for the admin section inside this folder. you can >> even have same name models/ controllers as the public site inside >> this >> folder. >> >> Not sure if this is what you asked for - but maybe it will help. > > > --~--~---------~--~----~------------~-------~--~----~ 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
