The database.yml.example has both production and development databases set to be 'dashboard'. If you just copy this and run `rake db:create:all` you'll get an error, and if you very mistakenly use the same database for development and production very bad things will happen.
This just changes them to be different in the example file so that it's easier to get started with sane defaults. Reviewed-by: Josh Cooper <[email protected]> Signed-off-by: Matt Robinson <[email protected]> --- Local-branch: ticket/next/maint-better_database_default_names config/database.yml.example | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/config/database.yml.example b/config/database.yml.example index ffc2159..02cddaf 100644 --- a/config/database.yml.example +++ b/config/database.yml.example @@ -41,7 +41,7 @@ # * Starting a server with: scipt/server -e production # * Running a rake task with: rake RAILS_ENV=production ... production: - database: dashboard + database: dashboard_production username: root password: encoding: utf8 @@ -53,7 +53,7 @@ production: # * Starting a server with: script/server # * Running a rake task with: rake ... development: - database: dashboard + database: dashboard_development username: root password: encoding: utf8 -- 1.7.3.1 -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
