Hey guys. Per my IT department's policies, I need to have two separate database users for my rails database - one for public intarweb functionality, one for authenticated users' functionality. The naive way to accomodate this would be to break the app up into two separate apps, but since they share the same models and resources, DRY suggests this isn't the proper thing to do.
Ideally, I'd like to have two separate database.yml files, and choose between them on a controller-by-controller basis. If this is a good strategy, how might I go about doing it? If not, how would y'all suggest I structure my app?
- donald