Runtime config attributes
  host
  port   (will it be possible for an app to have a separate port?)
  log    (i'm beginning to see that runtime level logs may be best. perhaps the runtime could have an optional "log viewer" waves app built in that could sort out stuff 'per app')
  debug
  synchronize?
  application (rack builder block)
  mime_types
  resources (routing)
  handler (rack handler)

App-specific config attributes
  database
  reloadable
  session
  dependencies
  *cache


Runtime config provided by top-level configurations
startup.rb specifies apps to load, perhaps using Dir["apps/*/lib/application.rb"]
Access runtime and app configs separately?
  Waves.config.synchronize?
  Blog.config.database


multi_1/
    apps/
        blog/
        wiki/
    configurations/
        default.rb # => Waves::Configurations::Default
        development.rb # => Waves::Configurations::Development
        production.rb # => Waves::Configurations::Production
    log/
    startup.rb


First app loaded is used for runtime config.
How/where do you specify the loading of apps?
*(don't like this method at all)
multi_2/
    blog/
        configurations/
        startup.rb
        ...
    pages/
        configurations/
        startup.rb
        ...
    wiki/
        configurations/
        startup.rb
        ...

same premise as multi_1, except it puts runtime config in a separate dir and
does away with the apps/ directory.
multi_3/
    blog/
       *configurations/
          development.rb
          production.rb
    wiki/
    runtime/
      configurations/
        default.rb # => Waves::Configurations::Default
        development.rb # => Waves::Configurations::Development
        production.rb # => Waves::Configurations::Production
      log/
      startup.rb