# Fat Free CRM settings are stored in three places, and are loaded in the following order:
#
# 1) config/settings.default.yml
# 2) config/settings.yml (if exists)
# 3) 'settings' table in database (if exists)
#
# Any settings in `config/settings.yml` will override those in
# `config/settings.default.yml`, and settings in the database table have the highest priority.
#
# This settings arrangement offers a lot of flexibility:
#
# * Developers can add new settings to the application with default values,
# without requiring the user to manually update setting files or run tasks.
# * No manual configuration is required to start the application after installation
# * IT administrators can change the default configuration by adding 'settings.yml'
# to their git repo, or by running SQL that updates the 'settings' table in the database.
# * Admin users can change settings via the admin interface, without needing to edit YAML files.
Unfortunately, we haven't had time to build the admin settings interface yet, since it hasn't been a very high priority.
Cheers,
Nathan
On Sat, Oct 6, 2012 at 6:49 AM,
<weston...@gmail.com> wrote:
Since I didn't get any feedback, I am going to go ahead an implement - initially pull settings from YAML file
- pull settings from database
Feedback is totally welcome.
On Thursday, September 6, 2012 6:30:10 AM UTC-5,
weston...@gmail.com wrote:
Spree uses a YML a file to store initial app settings, which are then stored as database entries. Once the app is running, settings can persist in the app via CRUD.
This seems like a good method for implementing settings in FFCRM.
How does this sounds to others?
--
You received this message because you are subscribed to the Google Groups "Fat Free CRM Developers" group.
To view this discussion on the web visit https://groups.google.com/d/msg/fat-free-crm-dev/-/oC9juFc5Q0IJ.