[Rails] To split, or not to split, that's a question.
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
zhiqiang.lei@gmail.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@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
0 Comments:
Post a Comment
Subscribe to Post Comments [Atom]
<< Home