Device Convention for Scope?

I’ve been using device for quite some times now. I was wondering a good
practice to design the application with scope. Usually I choose to
separate
the admin part and the user part. so there is two model Admin and User.

Admin functionality are scoped with Admin , And user functionality are
just
like the usual rails covention.
for instance in the controller there might be something like this

admin/documents_controller.rb
application_controller.rb
documents_controller.rb

so for example the the DocumentsController < ApplicationController
while ApplicationController < ActionController::Base

now let say I want the ApplicationController “like” for admin. What is
the
best way to implement this ?
maybe like Admin::DocumentsController < Admin::AdminController, and
Admin::AdminController < ActionController::Base maybe ?

this part get confusing if I perceive Admin as a resource, like managing
the admins. so it would be another controller like
Admin::AdminsController ?

have you been into this sort of scenario ? and how would you tackle the
problem ?

Thanks

Ahmy Y

On 27 March 2012 11:43, Ahmy Y. [email protected] wrote:

I’ve been using device for quite some times now. I was wondering a good
practice to design the application with scope. Usually I choose to separate
the admin part and the user part. so there is two model Admin and User.

I would not do it that way, I would have just users and roles,
probably using the cancan gem.

Colin

I would suggest you to use cancan gem instead of devise scope or
namespace, it would be easier to understand and implement.

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs