I’m using acts_as_authenticated for the front end facing part of my
site. I have a model called Customer. I now want to protect the admin
sides of things. I am thinking of using Ezra’s acl plugin
for this. My only problem is that I don’t want the model for admin
users to be called Customer, I’d rather it be called User or something
(call me pedantic
So, I could rename my Customer model to User and implement the above
plugin which will give me the authorization I want. But then I lose
the ability to do:
Instead it will be:
Also, for admin users, I just want to store their username and
password, not all the other associated data that goes with a customer.
Is this a use for STI? Can I somehow alias the User model so that it
can be accessed as Customer as well? Shall I just forget this and live
with the name User?
How do others approach the frontend/backend authorization scenario? I
would imagine it’s pretty common.