Rails new Application create "new" and not "Application"

Rails
1

Hello

I start using RoR on Ubuntu because I want to develop a little bit.

I installed ruby:

$>sudo apt-get install ruby

and it’s ok

I installed gem:

$>sudo apt-get install rubygem1.8

I try to install rails with gem:

$>sudo gem install rails

ERROR: While executing gem … (Gem::FilePermissionError)
You don’t have write permissions into the /var/lib/gems/1.8
directory.

so i installed via apt:

$>sudo apt-get install rails

and it’s ok.
Now I tried to start a new application:

$>mkdir ./RailsCode
$>cd RailsCode
$>rails new Application

build me “new” and not “Application”:

$>ls
new

also if I try to start server:

$>cd new
$/new>rails server

rails build up a application named “server”

$/new>ls
… … … … server … … …

what can I DOOOOOO???

2

Syntax for some of the command line tools have changed between Rails 2.x
and
3. The syntax you’re using is new as of Rails 3, so you should run

rails -v

to see what you’re running. If it’s anything before version 3, you need
to
change the syntax of your commands to

$> rails application
$> ./script/server

in order to do what you want to do.

3

On 19 February 2011 11:29, Pietro R. [email protected] wrote:

I installed gem:

so i installed via apt:

$>sudo apt-get install rails

This is not the best route unfortunately. You really do want to use
rubygems to manage the gems. This link seems to show a reasonable
route

Once you manage to get something working, before starting any serious
work, I would also highly recommend using rvm. It can be a little
fiddly to get working but is worth the effort.

One final point, Rails 3 with ruby 1.9.2 (on Ubuntu at least) seems to
have startup speed issues. At the moment it may be best to stick to
ruby 1.8.7 (which you may well already have installed via apt, which
is ok). Rails 3 is fine with 1.8.7.

Colin

4

Phil

On Sat, Feb 19, 2011 at 7:28 AM, Colin L. [email protected]
wrote:

directory.

That how-to looks good, but I’d recommend the latest rubygems (1.5.0); I
might be worthwhile to build it from source, if possible. It’s a trivial
process as long as gcc, et al., are installed.

Once you manage to get something working, before starting any serious
work, I would also highly recommend using rvm. It can be a little
fiddly to get working but is worth the effort.

Ditto on rvm. Well worth it for the benefits of having .rvmrc files in
your
project directories, different ruby versions, and different gemsets.

And yes, as someone said above: if you ran ‘rails new app’ and got a
directory named new, this definitely means you have Rails 2.x.x of some
sort, not Rails 3. That’s also why ‘rails server’ is not working, in
Rails 2
you start the server with ‘script/server’ …