Reputation: 931
I'm new to ruby and rails and i installed rails in to the ubuntu. but when i go to the start server by typing "rails s" it doesn't start and comes following message . but i can create a new project by command rails new new_project. please rails specialists help-out me.
root@ubuntu:~# rails s Usage: rails new APP_PATH [options] Options: -j, [--javascript=JAVASCRIPT]
# Preconfigure for selected JavaScript library # Default: jquery -m, [--template=TEMPLATE] # Path to an application template (can be a filesystem path or URL) [--dev]
# Setup the application with Gemfile pointing to your Rails checkout -J, [--skip-javascript] # Skip JavaScript files [--edge]
# Setup the application with Gemfile pointing to Rails repository -G, [--skip-git]
# Skip Git ignores and keeps -d, [--database=DATABASE]
# Preconfigure for selected database (options: mysql/oracle/postgresql/sqlite3/frontbase/ibm_db/sqlserver/jdbcmysql/jdbcsqlite3/jdbcpostgresql/jdbc)
# Default: sqlite3 -b, [--builder=BUILDER]
# Path to a application builder (can be a filesystem path or URL) -r, [--ruby=PATH]
# Path to the Ruby binary of your choice
# Default: /usr/bin/ruby1.8 [--old-style-hash]
# Force using old style hash (:foo => 'bar') on Ruby >= 1.9 [--skip-gemfile]
# Don't create a Gemfile -O, [--skip-active-record]
# Skip Active Record files [--skip-bundle] # Don't run bundle install -T, [--skip-test-unit]
# Skip Test::Unit files -S, [--skip-sprockets]
# Skip Sprockets files Runtime options: -q, [--quiet]
# Supress status output -f, [--force]
# Overwrite files that already exist -s, [--skip]
# Skip files that already exist -p, [--pretend]
# Run but do not make any changes 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
Upvotes: 14
Views: 26058
Reputation: 11
I am also new to Ruby on rails. I find the same issue when accidentally my PC shutdown. I fix it by following steps.
Create a new application. Rails new demo --Database=postgresql
Copy the Bin folder of new Demo app.
Remove the Bin folder of old App(That showing error)
Paste the New bin folder from Demo App to old App.
Start the server Rails server
Note you can copy the bin folder from Github. https://github.com/hoovercj/depot
Upvotes: 1
Reputation: 2867
I ran into this problem and was confused for a minute until I realized I accidentally deleted my bin folder.
How to fix it:
cd
back out of the root of the Rails app.rails new name_of_your_app
-- make sure it's the same name as the directory that already exists.n
for "no" each time it asks. n
for everything else it will keep everything else.application.html.haml
file, and so Rails also generated an application.html.erb
file for me in views/layouts
which I didn't need and so deleted. Notice any other files that were generated and delete any you don't want.rails s
to start the WEBrick server.Upvotes: 1
Reputation: 96614
Once you have created the project and cd
'd into it:
Use script/server
if you are on rails version 2.x
Use script/rails server
if you are on rails version 3.x
Use bin/rails server
if you are on rails version 4.x
Upvotes: 5
Reputation: 10829
A better method is to update your bin using following command
bundle exec rake rails:update:bin
Upvotes: 34
Reputation: 83680
You need to create a new Rails app (unless you already have one)
rails new my_app
Go to your app directory
cd my_app
Start the server in that directory
rails s
Upvotes: 11
Reputation: 11
Before starting the rails server, you have to cd into the directory of your application. That's because the server needs to know which application it's supposed to be serving.
Upvotes: 1