Migrating existing app to TheRole about the_role

[the-teacher]

@Svashta Hello, Mitja!

is it possible to integrate the role management panel with my own skin?

yeah. that is why the solution was split into a few parts. To provide another view you can fork this gem https://github.com/TheRole/the_role_management_panel and rework it completely. You can use any CSS, JS solution to provide required view of management panel. Any changes in View part will not affect backend part of TheRole gem. Feel free to change anything in the view part of the solution.

Also Rails provides a way to define places where App looks for view templates and css/js assets. You can use the original gem https://github.com/TheRole/the_role_management_panel and redefine all view files in your main app.

Please take a look at docs for config.assets.paths and prepend_view_path

MyRailsApp::Application.config.assets.paths.unshift("#{Rails.root}/#{app/assets/}")

if respond_to?(:prepend_view_path)
  prepend_view_path "PATH_TO_ALTERNATIVE_VIEWS"
end

what do i need to do to replace cancancan/rolify with TheRole (devise so of course stay)

• ready the docs for TheRole https://github.com/TheRole/docs
• create a small test app to play with TheRole and analyze how it works. This one test app will be a good help for you https://github.com/TheRole/rails5dummy

My personal practice

I'm pretty sure TheRole is amazing solution for my own purposes. And any another gem will be amazing if you know how to use it.

But, you know, I think, the best solution is the simplest solution. I've seen many huge Rails apps for really huge companies, and you know, usually the best way to manage permissions is just to have a field in a database like this:

User.role = "user" # manager | admin | editor

class User
  def admin?
     role == "admin"
  end

  def editor?
     role == "editor"
  end

  def manager?
     role == "manager"
  end
end

Feel free ask any question and Good luck!