Chamber can load itself from any path that's passed in to it
Chamber loads the settings.yml file from the base path by default
Delegate all methods to the instance
Add core extensions for a couple Hash methods so we don't have to include an external library
Allow settings to be accessed through Hash-like syntaxe
Switch to Hashie::Mashes to get the object-like accessing as well as indifferent key access
Use method missing to delegate any message sent to Chamber as a message for the underlying Hash
Decompress a few lines for better readability
Settings may be accessed through object-like notation
Allow the instance to be accessed via 'env'
Allow settings to contain ERB so that they can contain dynamic elements
Allow the environment to override values in the settings files
Whitespace
Add the ability to load files based on namespaces
If the namespaces DSL is called multiple times, it clears the namespaces each time
Make the settings accessor public
Make sure settings are cleared every time they are loaded
Refactoring namespace loading. Let it be called multiple times, just check for unique values only
Forgot to make sure that if a method does not exist on settings, it should still raise a NoMethodError
Make sure to reset the singletons after every spec