Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
|Failed to load latest commit information.|
Modifications to AppConfig plugin by Eugene Bolshakov to add more functionality and make sure that parsing exceptions are thrown AppConfig plugin by Eugene Bolshakov, email@example.com, http://www.taknado.com The plugin is based on the idea described here: http://kpumuk.info/ruby-on-rails/flexible-application-configuration-in-ruby-on-rails/lang-pref/en/ 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 An example of a config file: common: admin_email: firstname.lastname@example.org 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.xml_rpc_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.