Are you saying that for now, you want to use ActiveRecord as well as MySQL? You can change directory to your app's directory and run: $ rails new my-existing-app-name --database=mysql . It will try to generate all of the files and there will be conflicts. You can keep saying No to the overwrite prompts and it will eventually get to database.yml, which you can create/overwrite.
On Thursday, November 13, 2014 5:04:53 PM UTC-8, Ruby-Forum.com User wrote: > > I generate new rails application with --skip-activerecord, because I'm > going to use with MongoDB. > But right now I want my APP to support MySQL as well. > Any solutions? > > -- > Posted via http://www.ruby-forum.com/. > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-talk@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/632e97a9-fd71-49c6-bfad-5b26e93adbce%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
