Contents

= AppConfig

It allows to have a file (config/config.yml) with application configuration parameters.
It should have a "common" section with all parameters along with default values and can also
contain a section for each of the rails environments (development, test, production, or 
your custom one). The values from the current environment section will override the values in the 
"common" section.

If some developer needs his own specific values for his working copy, he can simply create 
a config/config.local.yml file and override any value there, again having a "common" section 
and a section for each environment. 

Nothing is mandatory (files, sections) -- you just have what you really need. The files are parsed with ERB,
so they can contain some Ruby

== Example usage

  common:
    admin_email: [e-mail]
    xml_rpc_url: http://domain.com:8000/
    media_path: <%= RAILS_ROOT %>/tmp/media

  development:
    xml_rpc_url: http://localhost:8000/

  test:
    xml_rpc_url: http://localhost:8008/

Then, in the application you can use the config parameters like this:

  #{Conf.site_url}

So it means that you've got a Config object which holds all the configuration parameters defined. 
It doesn't allow to change the values in the application code, BTW.

== Authors and credits

Authors::      Eugene Bolshakov, 
Site URL::     http://www.taknado.com
Based on::     http://kpumuk.info/ruby-on-rails/flexible-application-configuration-in-ruby-on-rails/lang-pref/en/

Version data entries

2 entries across 2 versions & 1 rubygems

Version	Path
scotch-app_config-1.5.0	README.rdoc
scotch-app_config-1.5	README.rdoc