On 4 Aug., 23:34, Philip Hallstrom <[email protected]> wrote:
> 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.
>
And there are no problems to expect this way? I want to create a
subdomain with a route to the admin section. I've already tested the
ssl and subdomain things in rails, they're looking great.
Back to my first question: Is this the only recommandable way to build
an admin section? Is it possible to create two apps and one is
"linked" to the other? What I mean is: The public app would use some
things (like models) from the admin app, and all rails magic would be
available.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
