obviously :D I was just thinking that could reuse configuration in your database.yml (for credentials, database location, etc)
On Tuesday, February 8, 2011 8:51:32 AM UTC+2, jim wrote: > > no rake task needed. if you have the mysqldump, use the following (assuming > the dump is dump.sql) > > mysql -u root -p database < dump.sql > > On Tue, Feb 8, 2011 at 2:03 PM, Nikos Dimitrakopoulos > <[email protected]>wrote: > >> How do you do it? Regular sql dump tool (like mysqldump) and then some >> rake task for importing it on the development database? >> >> On Tuesday, February 8, 2011 1:42:22 AM UTC+2, paul wrote: >> >>> Do you have your app deployed? What I do is populate development with >>> a recent backup of my live server every once in a while. That way I'm >>> seeing what the users are (at least until it drifts). >>> >>> On Mon, Feb 7, 2011 at 5:51 PM, Hesham <[email protected]> wrote: >>> > What would be the best way to populate a development database for a >>> > Rails 3 app? I have looked at faker, but it seems that development has >>> > stopped, any other options? >>> > >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Ruby on Rails: Talk" 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-talk?hl=en. >> > > > > -- > ------------------------------------------------------------- > visit my blog at http://jimlabs.heroku.com > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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-talk?hl=en.
