Rake commands not recognized

Question

UPDATE:

So it turns out the issue is has to do with me corrupting confg/boot.rb. Details are in the answer below.

So basically rake stopped working. I'm trying to add a new model, and if I then run

rake db:migrate

I get:

Error: Command 'db:migrate' not recognized

I'm pretty sure rake is correctly installed and sourced though. If I run:

rake

I get the normal 'man' page starting with

Usage: rails COMMAND [ARGS]...The most common rails commands are...

Interestingly enough it also spits this out at the bottom:

.../db/schema.rb doesn't exist yet. Run 'rake db:migrate' to create it, then try again. If you do not intend to use a database, you should instead alter .../config/application.rb to limit the frameworks that will be loaded.

I do intend to use a database, so I'd love to get rake working...

Am I missing something obvious?

Thanks ahead of time!

Are you sure you are not mistaking the commands `rails` and `rake`? What's the output of `which rake`? — mechanicalfish, Dec 04 '13 at 00:05
@mechanicalfish `which rake` returns `/.rvm/gems/ruby-2.0.0-p247@global/bin/rake` — cjhin, Dec 04 '13 at 00:09
@ShaunFrostDukeJackson `rake db:create` gives me `Error: Command 'db:create' not recognized` — cjhin, Dec 04 '13 at 00:10
@cjhin This is weird. Come to the [rails chat room](http://chat.stackoverflow.com/rooms/5676/ruby-on-rails) I'll try to help you. — mechanicalfish, Dec 04 '13 at 00:18
@mechanicalfish ah... apparently I don't have a high enough reputation to talk in the chat room? — cjhin, Dec 04 '13 at 00:20
This may sound daft..But have you done a `bundle install` then tried a `bundle exec rake db:migrate` — Deej, Dec 04 '13 at 02:26

score 2 · Answer 1 · answered Dec 04 '13 at 00:23

2

Did you try it via bundle?

bundle exec rake db:migrate

answered Dec 04 '13 at 00:23

BvuRVKyUVlViVIc7

11,641
9
59
111

Unfortunately I'm still getting the `Error: Command 'db:migrate' not recognized`. Thanks though! – cjhin Dec 04 '13 at 00:25
I added it to the original post, hope that helps! – cjhin Dec 04 '13 at 01:33

score 0 · Accepted Answer · edited May 23 '17 at 11:45

0

So it turns out the issue is due to me incorrectly following instructions on a SO post regarding changing the port that rails server binds to.

Basically I incorrectly modified config/boot.rb which somehow corrupted the behavior of rake.

Specifically I completely misread and mashed together the top two answers, appending the following code to config/boot.rb instead of placing it in a standalone script.

# THIS IS NEW:
require "rails/commands/server"
module Rails
  class Server
    def default_options
      super.merge({
        :Port        => 10524,
        :environment => (ENV['RAILS_ENV'] || "development").dup,
        :daemonize   => false,
        :debugger    => false,
        :pid         => File.expand_path("tmp/pids/server.pid"),
        :config      => File.expand_path("config.ru")
      })
    end
  end
end
# END OF CHANGE
require 'rails/commands'

Sorry guys. Thanks for the help though!

edited May 23 '17 at 11:45

Community

1
1

answered Dec 05 '13 at 03:08

cjhin

235
4
16

Hey @cjhin I just did the same thing. How'd you fix it? – j0e Jan 09 '14 at 04:55
@j0e When you say "the same thing", do you mean the same issue with incorrectly modifying config/boot.rb? – cjhin Jan 09 '14 at 04:57
Yes. I needed to set my server into using port 9999 by default for some testing and it borked my rake command. I editing the boot.rb back to what it was before but it's still messed up. How'd you fix yours? – j0e Jan 09 '14 at 07:43
honestly I think I just created a new rails app and ported over the data I needed... sorry that's probably not the answer you were hoping for – cjhin Jan 10 '14 at 07:45
Thanks cjhin that's what I decided to do as well. – j0e Jan 10 '14 at 07:55

Rake commands not recognized

2 Answers2