Thanks, I thought about that. But in this way Admin::TicketsController still 
cannot share some views of TicketsController well. And due to the name 
convention, when I use form builder with a ticket, it will use the ticket path 
without admin prefix defaultly.

On Jul 21, 2012, at 1:29 PM, thiagocifani wrote:

> And about the admin portal feature, you shows set every resource to a 
> namespace called admin. Your routes will look like something like:
> 
> namespace :admin do
>     resources :tickets
> end
> 
> So you should set up a controller inside the namespace admin:
> 
> Class Admin::TicketsController < Application Controller
> 
> 
> end
> 
> 
> Hope this helps you!
> 
> Regards
> 
> Sent from my iPhone
> 
> On 20/07/2012, at 22:39, Everaldo Gomes <[email protected]> wrote:
> 
>> Hi,
>> 
>> maybe you could create a Rails Engine.
>> 
>> Take a loot at the Railscasts site 
>> http://railscasts.com/episodes/277-mountable-engines
>> 
>> Best Regards,
>> 
>> Everaldo
>> 
>> On Fri, Jul 20, 2012 at 10:04 PM, Zhi-Qiang Lei <[email protected]> 
>> wrote:
>> Hi,
>> 
>> I'm working on a Rails application. Recently my client is asking for an 
>> admin portal, which should be able to manage ticket as the one for the 
>> original one, and have some admin specific features additionally. And their 
>> authentications are different, the user portal uses Devise, while the admin 
>> portal uses basic HTTP authentication. My intuition prefers to create a 
>> standalone Rails project for admin portal, but they do share something like 
>> model, and forms. I'm worrying that split the project would break DRY. Does 
>> anyone can give me some advices? Thanks.
>> 
>> Best regards,
>> Zhi-Qiang Lei
>> [email protected]
>> 
>> --
>> 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 https://groups.google.com/groups/opt_out.
>> 
>> 
>> 
>> 
>> -- 
>> 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 https://groups.google.com/groups/opt_out.
>>  
>>  
> 
> 
> -- 
> 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 https://groups.google.com/groups/opt_out.
>  
>  


Best regards,
Zhi-Qiang Lei
[email protected]

-- 
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 https://groups.google.com/groups/opt_out.


Reply via email to