Loading config YAML into merb process for the life of the process

[Tim Perrett]

Hey Chaps,

Forgive me for not fully understanding the inner workings of merb, but  
I would like to read in a YAML configuration file once when the  
application is booted rather than reading it every time it is used (as  
presumably the overhead in doing that is significant?) - I had  
presumed this is how both Merb and rails do it for there database.yml  
config files (hence its a requirement to restart the process if you  
change the DB config) but after looking at the rails trunk there seems  
to be nothing obvious going on that would cache the returned  
configuration.

Are there hooks available so that gem plugins for merb can run code  
when the application is at different parts of booting? If so, how on  
earth would I then store said configuration?

Many thanks for any pointers

Tim