title: Why doesn't "rails s" work from the app directory?
body: <p>I'm in my app folder, but the command <code>rails s</code> is not working. I read through quite a few posts on Stack Overflow, and most of them seem to be from users who are not in their app directory.</p>
  
  <p>In addition, I built a few other apps. I checked those, and the Rails server works for all of those apps. This is the only one where I can't get it to launch.</p>
  
  <p>Output of <code>which rails</code>:</p>
  
  <pre><code>/Users/jmcrist/.rvm/gems/ruby-2.0.0-p247/bin/rails
  </code></pre>
  
  <p>Output of <code>rails s</code>:</p>
  
  <pre><code>MacBook-Pro:first_app jmcrist$ rails s
  Usage:
    rails new APP_PATH [options]
  
  Options:
    -r, [--ruby=PATH]              # Path to the Ruby binary of your choice
                                   # Default: /Users/jmcrist/.rvm/rubies/ruby-2.0.0-p247/bin/ruby
    -b, [--builder=BUILDER]        # Path to a application builder (can be a filesystem path or URL)
    -m, [--template=TEMPLATE]      # Path to an application template (can be a filesystem path or URL)
        [--skip-gemfile]           # Don't create a Gemfile
        [--skip-bundle]            # Don't run bundle install
    -G, [--skip-git]               # Skip Git ignores and keeps
    -O, [--skip-active-record]     # Skip Active Record files
    -S, [--skip-sprockets]         # Skip Sprockets files
    -d, [--database=DATABASE]      # Preconfigure for selected database (options: mysql/oracle/postgresql/sqlite3/frontbase/ibm_db/sqlserver/jdbcmysql/jdbcsqlite3/jdbcpostgresql/jdbc)
                                   # Default: sqlite3
    -j, [--javascript=JAVASCRIPT]  # Preconfigure for selected JavaScript library
                                   # Default: jquery
    -J, [--skip-javascript]        # Skip JavaScript files
        [--dev]                    # Setup the application with Gemfile pointing to your Rails checkout
        [--edge]                   # Setup the application with Gemfile pointing to Rails repository
    -T, [--skip-test-unit]         # Skip Test::Unit files
        [--old-style-hash]         # Force using old style hash (:foo =&gt; 'bar') on Ruby &gt;= 1.9
  
  Runtime options:
    -f, [--force]    # Overwrite files that already exist
    -p, [--pretend]  # Run but do not make any changes
    -q, [--quiet]    # Suppress status output
    -s, [--skip]     # Skip files that already exist
  
  Rails options:
    -h, [--help]     # Show this help message and quit
    -v, [--version]  # Show Rails version number and quit
  
  Description:
      The 'rails new' command creates a new Rails application with a default
      directory structure and configuration at the path you specify.
  
      You can specify extra command-line arguments to be used every time
      'rails new' runs in the .railsrc configuration file in your home directory.
  
      Note that the arguments specified in the .railsrc file don't affect the
      defaults values shown above in this help message.
  
  Example:
      rails new ~/Code/Ruby/weblog
  
      This generates a skeletal Rails installation in ~/Code/Ruby/weblog.
      See the README in the newly created application to get going.
  </code></pre>
  
  <p>I'm working through Hartl's Rails Tutorial, and he makes quite a few modifications to the gemfile. I am wondering if this might be the cause?</p>
  
  <pre><code>source 'https://rubygems.org'
  
  gem 'rails', '3.2.13'
  
  group :development do
    gem 'sqlite3', '1.3.5'
  end
  
  
  # Gems used only for assets and not required
  # in production environments by default.
  group :assets do
    gem 'sass-rails',   '3.2.5'
    gem 'coffee-rails', '3.2.2'
  
    gem 'uglifier', '1.2.3'
  end
  
  gem 'jquery-rails', '2.0.2'
  
  group :production do
    gem 'pg', '0.12.2'
  end
  </code></pre>