Jay,

I'm in the process of going through the railstutorial.org chapters and
providing some coaching for some clients of mine that want to get up to
speed on rails. (and the railstutorial is a great way to do that!)

I would start with the most basic steps you can, and make sure that you use
rvm to keep your gems from conflicting.

(I assume you are talking about just getting the basic app he is describing
to work, not upgrading some other app you already had...with various
dependencies and issues not yet revealed to us)

It looks like you are not having a problem with heroku, but rather your
local setup. (so you might not get much response from this mailing list)

Here are the steps that I recommend

  rvm install 1.9.2  # if you hadn't already
  mkdir rails_tutorial
  cd rails_tutorial
  rvm use 1.9.2

#create a gemset that will hold all the gems for the rails_tutorial chapters

   rvm gemset create rails3tutorial

# write out a .rvmrc file that will ensure that whenever you are in this
directory, you use this gemset

   echo 'rvm use 1.9.2-p0@rails3tutorial' > .rvmrc

# cd out, and then back in again to have rvm ask you if you want to use this
gemset
    cd ../
    cd rails_tutorial
  # answer yes

# now we can install gems, and they will go into that gemset
  gem install bundler heroku
  gem install rails --version 3.0.3

# now let's build an app
  rails new first_app
  cd first_app
# start it up
  rails server
#just check that you have the index page
  open http://localhost:3000

# if we have something that works, lets create a local repo to keep track of
our changes
  git init
  git add .
  git commit -am 'initial commit'

# push it to heroku and see it live
  heroku create
  git push heroku master
 heroku open

#from there I'd do the scaffold step, check it locally and then push to
heroku and heroku rake db:migrate

Now I'm not on ubuntu, so maybe you are running into an issue I haven't
seen. At this point you may get better help from other people that are doing
the tutorial, and just follow what they do step by step.

Also, if you ever do 'sudo' gem install while using rvm you may cause issues
that can be hard to untangle. (gems not in the right place, wrong gems
loading, conflicts, etc)

good luck

On Thu, Dec 16, 2010 at 6:42 PM, Jay Godse <jgo...@gmail.com> wrote:

> I have been fighting the Rails installation. Ruby1.8.7 on  Rails 2.3.x
> and heroku were working fine. Then I decided to upgrade to Ruby 1.9.2
> and Rails 3..0.3, using the instructions in Michael Hartl's tutorial
> at http://railstutorial.org/chapters/beginning. I got to the point of
> using autotest, but it didn't install, so I kept debugging and
> backtracking and adding librarries and backtracking...until I took all
> Ruby, Rails, RVM off my system (Ubuntu 10.4) and started with a fresh
> install of Ruby 1.9.2. I then installed Rails, but a few things went
> wrong.
>
> rails -v and "rails new doodad" worked to create a new app, but "rails
> server" did not work. It said,
>
> jgodse@ubuntu1:~/rapps/hartl/doodad$ rails server
> rails server
> /home/jgodse/rapps/hartl/doodad/config/boot.rb:9:in `rescue in <top
> (required)>': uninitialized constant Object::Bundler (NameError)
>        from /home/jgodse/rapps/hartl/doodad/config/boot.rb:5:in `<top
> (required)>'
>        from script/rails:5:in `require'
>        from script/rails:5:in `<main>'
> jgodse@ubuntu1:~/rapps/hartl/doodad$
>     gem list --local
>
> *** LOCAL GEMS ***
>
> abstract (1.0.0)
> actionmailer (3.0.3)
> actionpack (3.0.3)
> activemodel (3.0.3)
> activerecord (3.0.3)
> activeresource (3.0.3)
> activesupport (3.0.3)
> arel (2.0.6)
> builder (2.1.2)
> bundler (1.0.7)
> configuration (1.2.0)
> diff-lcs (1.1.2)
> erubis (2.6.6)
> heroku (1.14.10)
> i18n (0.5.0)
> json_pure (1.4.6)
> launchy (0.3.7)
> mail (2.2.12)
> mime-types (1.16)
> nokogiri (1.4.4)
> polyglot (0.3.1)
> rack (1.2.1)
> rack-mount (0.6.13)
> rack-test (0.5.6)
> rails (3.0.3)
> railties (3.0.3)
> rake (0.8.7)
> rest-client (1.6.1)
> rspec (2.3.0, 2.1.0)
> rspec-core (2.3.0, 2.1.0)
> rspec-expectations (2.3.0, 2.1.0)
> rspec-mocks (2.3.0, 2.1.0)
> rspec-rails (2.1.0)
> sqlite3-ruby (1.3.2)
> thor (0.14.6)
> treetop (1.4.9)
> tzinfo (0.3.23)
> webrat (0.7.1)
> jgodse@ubuntu1:~/rapps/hartl/doodad$
>
>
> It seems that bundler is missing even though it is installed. Another
> time, I fired up rails, and it was looking for /usr/bin/ruby1.8 even
> though it is not installed on my system.
>
> I have fought this battle along a few differrent paths. My question,
> Is there a recipe that can get me a Ruby1.9.2/Rails3.0/postgresql
> Rails stack up and running.
>
> Or alternatively, if you have a Ubuntu 10.4 or Debian system up and
> running, could you give me a list of gems, libraries, programs, and
> environment variables that make your system happen?
>
>
> Thanks,   Jay
>
> --
> You received this message because you are subscribed to the Google Groups
> "Heroku" group.
> To post to this group, send email to heroku@googlegroups.com.
> To unsubscribe from this group, send email to
> heroku+unsubscr...@googlegroups.com<heroku%2bunsubscr...@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/heroku?hl=en.
>
>


-- 
-John

-- 
You received this message because you are subscribed to the Google Groups 
"Heroku" group.
To post to this group, send email to heroku@googlegroups.com.
To unsubscribe from this group, send email to 
heroku+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/heroku?hl=en.

Reply via email to