Skip to content

Why to use cantango

kristianmandrup edited this page Nov 10, 2011 · 2 revisions

Why use Cantango?

  • Performance
    • advanced multi-level rules caching
  • Partition rules in logical containers
    • place permission rules in separate classes, fx for roles and role groups
  • Reuse rules
    • via inheritance and licenses (rules mix-ins)
  • Engines
    • Use the built-in rule engines or add your own
  • Maintain and administrate permissions
    • store and load permissions from a rules store (fx a yaml file)
    • Mount the cantango editor to your app, and administrate permissions from a web UI
  • Masquerade
    • let some users masquerade as others
  • User accounts
    • integrate accounts for sub-apps with your access control logic
  • Guest users
    • visitors not logged in are assigned a Guest user
  • Devise integration
    • support for multiple devise users, not just #current_user
  • No intrusion with existing CanCan or Devise functionality
    • avoid having to monkey patch!
  • Advanced configuration
    • lots configuration options using a nice DSL
  • Extensible
    • designed to be easy to customize to your needs

Clone this wiki locally