I have just installed Ruby on Rails package that found in http://rubyinstaller.org/ (This is my first attempt to set up the ruby on rails workstation in my xp sp3 system.). The installation process went perfectly without any errors. I started the server using it's console. Server is started but http://localhost:3000 shows an error page (page not found).
I have following display in the console.Am i missing anything?
#Rails Environment Configuration.
---
git:
user.name: XYZ
user.email: xyzuser
version: git version 1.8.1.msysgit.1
ruby:
bin: C:/RailsInstaller/Ruby1.9.3/bin/ruby.exe
version: ruby 1.9.3p392 (2013-02-22) [i386-mingw32]
rails:
bin: C:/RailsInstaller/Ruby1.9.3/bin/rails.bat
version: Rails 3.2.13
ssh:
public_key_location: C:\Documents and Settings\xyz/.ssh/id_rsa.pub
public_key_contents: ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEArYKMRvMHxKJ2R//5viqQp
D4IQhVcKZhhbfvZGzDOXF1M//pewAQDK2x9y8T8irvatgmDMCYB5L2uZiyXwG3gPm6Bfw44mCHhNP8xN
bT2OSDnvIoZcFVfmQExZmwWcSNqm0NionObUV+IFKvfjg9bOPl4GBUqSXSTlUmAn/wQq0c/m+GoJwDlI
dV/h69dq4tHYwpCMFUZ9k4LqR4VICktV5Fi1VQA14u4Y9kOWAAyAfzeXnOzcpkbYxgjbCvAf20gM6lSL
9NvNsLuzI5yLxhI5wAmZbK+11zgNmx019tbv1uHvZRV2Z53aWpErtuvipAieQ977U4kYQPMyFf8g8BKd
Q== XYZ<xyzuser>
C:\Sites>
And the console output when the server is started is:
C:\Sites>rails s
Usage:
rails new APP_PATH [options]
Options:
-r, [--ruby=PATH] # Path to the Ruby binary of your choice
# Default: C:/RailsInstaller/Ruby1.9.3/bin/ruby
.exe
-b, [--builder=BUILDER] # Path to a application builder (can be a files
ystem path or URL)
-m, [--template=TEMPLATE] # Path to an application template (can be a fil
esystem 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 t
o your Rails checkout
[--edge] # Setup the application with Gemfile pointing t
o Rails repository
-T, [--skip-test-unit] # Skip Test::Unit files
[--old-style-hash] # Force using old style hash (:foo => 'bar') on
Ruby >= 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.
C:\Sites>
Thank you everyone. Finally I got it worked. The problem was the Gemfile in my test_app folder. I commented on the line gem 'uglifier', '>= 1.0.3' and i got it worked. Hopefully it will work further as well and let me move on.
You have to cd in the directory of the created rails project, then rails s should work fine.
This means also, that the server has not started yet. Please read carefully the output of the console commands, most of the time they tell you what they do, or why they don't work as expected.
First of all you have to create a new rails project. I think that C:/Sites is not your rails project directory.
rails new test_app
It will create a rails project in your directory. than go to cd test_app. and try to start your server.
Hope it will work.
Server is not started. You need to navigate to your rails app folder, install needed gems and start the server:
cd <your app folder>
bundle install
rails s
Related
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
A better method is to update your bin using following command
bundle exec rake rails:update:bin
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
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
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.
I ran into this problem and was confused for a minute until I realized I accidentally deleted my bin folder.
How to fix it:
Backup your app.
cd back out of the root of the Rails app.
Run rails new name_of_your_app -- make sure it's the same name as the directory that already exists.
Rails will build the folder again, asking you if you want to overwrite files, hit n for "no" each time it asks.
Rails will add the missing bin files, whereas if you hit n for everything else it will keep everything else.
In my case I was using HAML with an 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.
Run rails s to start the WEBrick server.
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
Any suggestions on why am I getting this? My ruby version is ruby 1.8.7 (2011-06-30 patchlevel 352) [i686-darwin11.1.0] and rails version is Rails 3.1.1. I have done bundle install and gem update --system.
➜ expertiza git:(master) ✗ rails server
Usage:
rails new APP_PATH [options]
Options:
-j, [--javascript=JAVASCRIPT] # Preconfigure for selected JavaScript library
# Default: jquery
-r, [--ruby=PATH] # Path to the Ruby binary of your choice
# Default: /Users/vsingh3/.rvm/rubies/ruby-1.8.7-p352/bin/ruby
-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
-G, [--skip-git] # Skip Git ignores and keeps
-m, [--template=TEMPLATE] # Path to an application template (can be a filesystem path or URL)
-b, [--builder=BUILDER] # Path to a application builder (can be a filesystem path or URL)
[--old-style-hash] # Force using old style hash (:foo => 'bar') on Ruby >= 1.9
[--skip-gemfile] # Don't create a Gemfile
-d, [--database=DATABASE] # Preconfigure for selected database (options: mysql/oracle/postgresql/sqlite3/frontbase/ibm_db/sqlserver/jdbcmysql/jdbcsqlite3/jdbcpostgresql/jdbc)
# Default: sqlite3
-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:
-f, [--force] # Overwrite files that already exist
-s, [--skip] # Skip files that already exist
-p, [--pretend] # Run but do not make any changes
-q, [--quiet] # Supress status output
Rails options:
-v, [--version] # Show Rails version number and quit
-h, [--help] # Show this help message and quit
Description:
The 'rails new' command creates a new Rails application with a default
directory structure and configuration at the path you specify.
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.
Thanks!
I encountered this same problem a while back and I think it was due to an outdated gemfile. Make sure you have the same version of rails listed in your gemfile as is installed on your machine.
You should look in to using RVM if you don't currently. It will keep all of your environments for different applications separate (including ruby versions and gem lists/versions).
I run rails new search in my console, and I get all of this:
Usage:
rails new APP_PATH [options]
Options:
-J, [--skip-prototype] # Skip Prototype files
-T, [--skip-test-unit] # Skip Test::Unit files
-G, [--skip-git] # Skip Git ignores and keeps
-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
-b, [--builder=BUILDER] # Path to an application builder (can be a filesystem path or URL)
[--edge] # Setup the application with Gemfile pointing to Rails repository
[--skip-gemfile] # Don't create a Gemfile
-d, [--database=DATABASE] # Preconfigure for selected database (options: mysql/oracle/postgresql/sqlite3/frontbase/ibm_db)
# Default: sqlite3
-r, [--ruby=PATH] # Path to the Ruby binary of your choice
# Default: /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby
-O, [--skip-active-record] # Skip Active Record files
Runtime options:
-q, [--quiet] # Supress status output
-s, [--skip] # Skip files that already exist
-f, [--force] # Overwrite files that already exist
-p, [--pretend] # Run but do not make any changes
Rails options:
-v, [--version] # Show Rails version number and quit
-h, [--help] # Show this help message and quit
Description:
The 'rails new' command creates a new Rails application with a default
directory structure and configuration at the path you specify.
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.
But it doesn't actually create the application. What's wrong here?
turns out I needed to install the rails gem again: gem install rails
Have you tried rails new ./search ?
I just tried it in windows, Ruby 1.9 w rails 3.0.9 and didn't have that problem.
If you're using RVM, try creating a new gemset and then install rails.
rvm gemset create better
rvm gemset use better
gem install rails -v x.x.x
rails new betterApplication
When I try to generate a new app with Rails 3.0.6 or 3.0.7 installed I just get the instructions for using the rails command. For some reason Rails seems to think that I have typed in the wrong syntax (which I haven't, of course). Everything works fine in 3.0.5 or lower, though. I run Ruby 1.9.2 and Ubuntu 10.04.
rails new app
Will result in:
Usage:
rails new APP_PATH [options]
Options:
-r, [--ruby=PATH] # Path to the Ruby binary of your choice
# Default: /usr/local/bin/ruby
-d, [--database=DATABASE] # Preconfigure for selected database (options: mysql/oracle/postgresql/sqlite3/frontbase/ibm_db)
# Default: sqlite3
-b, [--builder=BUILDER] # Path to an application builder (can be a filesystem path or URL)
-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
[--edge] # Setup the application with Gemfile pointing to Rails repository
[--skip-gemfile] # Don't create a Gemfile
-O, [--skip-active-record] # Skip Active Record files
-T, [--skip-test-unit] # Skip Test::Unit files
-J, [--skip-prototype] # Skip Prototype files
-G, [--skip-git] # Skip Git ignores and keeps
Runtime options:
-f, [--force] # Overwrite files that already exist
-p, [--pretend] # Run but do not make any changes
-q, [--quiet] # Supress status output
-s, [--skip] # Skip files that already exist
Rails options:
-v, [--version] # Show Rails version number and quit
-h, [--help] # Show this help message and quit
Description:
The 'rails new' command creates a new Rails application with a default
directory structure and configuration at the path you specify.
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.
try updating rubygems;
$ gem update --system
It seems running rvm rubygems current breaks this, at least for me.
I ran the command as it was mentioned here that it would get rid of all the deprecation warnings, running gem update --system fixes it, and brings back the deprecation warnings.
I'm trying to start the server on a rails app. with some apps it works fine, others I get this message:
rails s
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
-O, [--skip-active-record] # Skip Active Record files
[--dev] # Setup the application with Gemfile pointing to your Rails checkout
-J, [--skip-prototype] # Skip Prototype files
-T, [--skip-test-unit] # Skip Test::Unit files
-G, [--skip-git] # Skip Git ignores and keeps
-r, [--ruby=PATH] # Path to the Ruby binary of your choice
# Default: /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby
-m, [--template=TEMPLATE] # Path to an application template (can be a filesystem path or URL)
-b, [--builder=BUILDER] # Path to an application builder (can be a filesystem path or URL)
[--edge] # Setup the application with Gemfile pointing to Rails repository
Runtime options:
-q, [--quiet] # Supress status output
-s, [--skip] # Skip files that already exist
-f, [--force] # Overwrite 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
I'm using Rails 3.0.3 and ruby 1.8.7
I think you are trying to run Rails 2.x applications with this command. It will fail with this message. Since its consistently failing on certain apps, check if they are rails 2.x apps.
You can only run Rails 3.x applications with this command.
You must be missing script/rails file. Maybe you removed it by accident, or did something wrong while upgrading from Rails 2. Just copy it from a working project (or a new one).
My guess is that you are including a character after the 's'. If you type "Rails s" it will work but not if you type "Rails s ".
It is consistent with which apps work and which apps do not work?
I had the same issue. I figured out the problem was created by deleting rails 4.0.0beta1 from my system. I still had version 3.2 installed but I think the deletion deleted the scripts folder as well. After typing
gem install rails
It worked again. Maybe this helps someone.