> In an ideal world, I think Rails applications that have the right info > in config/database.yml would be able to create their own database > (something like rake db:create), load their own schema (rake > db:schema:load), and seed their own data (rake db:bootstrap) > automatically when run for the "first time".
I think this is being way too clever. Different applications will have different things they need to have happen before they can run. That might be gem dependencies, that might be ensuring a certain version of Ruby, it might be setting up seed data, it might be so many things that it's not worth standardizing. Just create script/setup and put in the README that people should run that when first installing the application. Problem solved, IMO. --~--~---------~--~----~------------~-------~--~----~ 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 [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
