search

ga-wdi-boston / capstone-project

Other
3 stars 29 forks source link

rake aborted #853

Closed 3point14guy closed 6 years ago

3point14guy commented 6 years ago

I am getting this error when I run heroku run rake db:migrate:

No Rakefile found (looking for: rakefile, Rakefile, rakefile.rb, Rakefile.rb)```

I ran again with --trace and got:

No Rakefile found (looking for: rakefile, Rakefile, rakefile.rb, Rakefile.rb) /usr/lib/ruby/vendor_ruby/rake/application.rb:684:in raw_load_rakefile' /usr/lib/ruby/vendor_ruby/rake/application.rb:94:inblock in load_rakefile' /usr/lib/ruby/vendor_ruby/rake/application.rb:176:in standard_exception_handling' /usr/lib/ruby/vendor_ruby/rake/application.rb:93:inload_rakefile' /usr/lib/ruby/vendor_ruby/rake/application.rb:77:in block in run' /usr/lib/ruby/vendor_ruby/rake/application.rb:176:instandard_exception_handling' /usr/lib/ruby/vendor_ruby/rake/application.rb:75:in run' /usr/bin/rake:27:in


Which, I don't know how to interpret. From Stack Overflow, I tried running ```bundle exec gem list rake``` and that returned only ```*** LOCAL GEMS ***```.  I bundle installed and tried ``heroku run rake db:migrate``` again and got the same result.  Another answer suggest to make sure I am in the correct directory, which I am.

What I do know is that I did the steps out of order and did the migrate after I set the secret keys.  Does this make a difference?  If so, do I just need to start over?
3point14guy commented 6 years ago

OK. I just tried doing it over again.

I ran git push heroku master again and it created a new app. When I did the heroku run rake db:migrate after that, it finished setting up my original app and not the new app created.

Closing as everything seems ok now.