# Ribica Back Office

Rails interface for administration

## Configuration

Configure config/database.yml to point to same database as config.rb in front office 

## Active scaffold

Customization documentation is here: http://activescaffold.com/

Example of generating scaffold for category model 

`rails g active_scaffold Category name:string`

## Handling shared models

Some of models will necesarrily be shared between front and back office. 
Migrations for those models *must be in front office* and 
back office will just have a model file with custom code if needed.
The reason is that we want front office to be standalone with a different
backoffice (for sellingtechnology to other businesses and stuff).

When generating active scaffold - migration is generated by default so it 
needs to be removed before using it.