Rethink configuration with settings.yml / database (system wide / plugins)
Reported by Nathan B | September 21st, 2011 @ 09:42 AM
Summary (what & why)
Work out a better way to deal with settings, and allow plugins to hook into the settings system.
What are the details?
- Default values are taken from settings.yml.
- Any setting can be changed in the admin interface, and is then saved to the database.
- Any settings in the database will override the defaults in settings.yml
- Provide a way to 'export settings in database to settings.yml'
When plugins are installed, they either write config to a new
file at ./config/crm_{plugin}_settings.yml, or they
would add a migration to db/migrations that appends their default
settings to the database.
No comments found
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Ruby on Rails CRM platform for Web 2.0 and beyond
Nathan B