Rails core - Oct 2012 - Default Rails setup convention between "bundle install" and "rake"

Question: Has anyone thought about or worked on creating default Rails
setup code for the work between "bundle install" and "rake"
for Rails
4.0?

    -- Sub-question: Is it part of Rails or rake or joint effort?

    -- My initial guess at what should be included:
        -a- Naming convention for hidden and multiple database.yml
files.
            -- template: database.<one_word>.yml
            -- if only one hidden file, then
                -- database.example.yml
            -- if one hidden file per database type, then
                -- use gem name as <one_word>
                -- database.sqlite3.yml, database.postgresql.yml,
                -- database.mysql2.yml, database.oracle.yml
        -b- A rake command that exercise the typical steps between
"bundle install" and "rake".
            -- Mostly, but not completely, involving database setup.
            -- Examples from existing projects:
                -- rake db:setup, rake setup, lots of rake
db:<one_step>
            -- Can you run this default rake command completely in
batch mode?

Thanks,
Al

PS. What is the right "rake" e-group to ask this question?

-- 
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Core" group.
To post to this group, send email to rubyonrails-core@googlegroups.com.
To unsubscribe from this group, send email to
rubyonrails-core+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rubyonrails-core?hl=en.