[Solved] typing ‘rails console’ doesn’t start?

I typed this:

>rails console

and got this:

Usage:
  rails new APP_PATH [options]

Options:
      [--skip-gemfile]        # Don't create a Gemfile
  -d, [--database=DATABASE]   # Preconfigure for selected database (options: mysql/oracle/postgresql/sqlite3/frontbase/ibm_db)
                              # Default: sqlite3
..
..
.

I’m following along the rails tutorial and got stuck on this.

I have rails 3.0 installed.

Enquirer: Blankman

||

Solution #1:

Are you in the root path of your app when you type $ rails console?

Tip: $ rails c is a shortcut for $ rails console

Respondent: Yannis

Solution #2:

In case anyone else hits this, my symptoms were:

I’d deployed my application with Capistrano 3

I cd’d into my application directory, and rails console didn’t work

Turned out I’d included the bin folder as a symlinked directory in my cap deploy, as follows:

set :linked_dirs, %w{log tmp/pids tmp/cache tmp/sockets vendor/bundle public/system}

… and my bin directory in ‘shared’ was empty.

Two fixes:

  • Ensure your linked bin directory has the correct contents (have a look inside your #{RAILS_ROOT}/bin directory for what this is, OR
  • Don’t symlink bin

I then re-deployed and it works.

Solution #3:

I just ran into this same problem while upgrading a Rails 2 app to Rails 3. When running rails console (or really rails [anything]) in my app’s root directory, I would see general rails new usage output (as Blankman referenced in the original question).

The problem was that I had not removed the old Rails 2 scripts from the script directory. After removing everything in the script directory and adding the script/rails file that is auto-generated in each new Rails 3 app, the rails command now works as expected.

In order to get the latest contents of the script/rails file, generate a new app and copy the file into your Rails 2 app that you’re upgrading. As of Rails 3.0.7, here’s what’s in this file:

#!/usr/bin/env ruby
# This command will automatically be run when you run "rails" with Rails 3 gems installed from the root of your application.

APP_PATH = File.expand_path('../../config/application',  __FILE__)
require File.expand_path('../../config/boot',  __FILE__)
require 'rails/commands'
Respondent: Nick

Solution #4:

I had this problem when I upgraded Rails 2 to 3 and was able to fix it by doing what Nick said, then also running bundle exec rails console production.

Respondent: Goro

Solution #5:

In Rails 2.3.x the command is script/console within a given Rails application directory to start a Ruby console with the default Rails environment loaded into memory. Not sure if Rails 3.0 is the same or not.

Respondent: Richard Cook

Solution #6:

You need to into the project directory and command rails console
eg:

D:workspace>rails blog
D:workspace>cd blog
D:workspacelog> rails c
loading en...
Respondent: kenny

Solution #7:

are you in a rails 3 app directory?

do you have multiple versions of rails installed?

try checking ‘which rails’, and make sure this is a rails 3 executable you are running – that usage looks like rails 2.x.

Respondent: Andrew Kuklewicz

Solution #8:

You are running the correct command (rails console), but you are most likely not in the working directory for this application. Change directory to the root of your rails application (beneath which you will find /scripts, /app, etc.), and the command should work as desired.

Note: Using script/console or ruby script/console is for earlier versions of Rails.

Respondent: eli

Solution #9:

In my case bin/rails c worked off my app root folder

Respondent: Arthur

The answers/resolutions are collected from stackoverflow, are licensed under cc by-sa 2.5 , cc by-sa 3.0 and cc by-sa 4.0 .

Leave a Reply

Your email address will not be published.