Re: How to get Ruby 1.9.2, Rails3, and PostgreSQL going?
Wanted to write the same, John is absolutely correct. If you use windows machine there is a similar option like RVM called Pik. I'm almost sure your gem has confilct. MAybe reinstalling rubygem simply solves the problem. Ruby1.9 already contains Rubygems, therefore it wild be like uninstall everything then reinstall. But RVM is still the best option: it also prevent problems later. Bests, gezope On jan. 26, 18:56, John McCaffrey john.mccaff...@gmail.com wrote: 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 openhttp://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 athttp://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
Re: How to get Ruby 1.9.2, Rails3, and PostgreSQL going?
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
How to get Ruby 1.9.2, Rails3, and PostgreSQL going?
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, jgo...@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' jgo...@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) jgo...@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 her...@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.
Haml / Ruby 1.9.2 Encoding issue
Hello, I am using ruby 1.9.2--p0 in my development environment, and my app works just fine. When i deploy to Heroku, i get Haml::Error - Invalid US-ASCII character \xE2: (haml):10 /home/slugs/330395_4dc8ceb_905f-8ba444ee-2b55-42da-98ee-04890afc4465/ mnt/.bundle/gems/ruby/1.9.1/gems/haml-3.0.22/lib/haml/engine.rb:91:in `block in initialize' /home/slugs/330395_4dc8ceb_905f-8ba444ee-2b55-42da-98ee-04890afc4465/ mnt/.bundle/gems/ruby/1.9.1/gems/haml-3.0.22/lib/haml/util.rb:463:in `rescue in block in check_encoding' /home/slugs/330395_4dc8ceb_905f-8ba444ee-2b55-42da-98ee-04890afc4465/ mnt/.bundle/gems/ruby/1.9.1/gems/haml-3.0.22/lib/haml/util.rb:460:in `block in check_encoding' /home/slugs/330395_4dc8ceb_905f-8ba444ee-2b55-42da-98ee-04890afc4465/ mnt/.bundle/gems/ruby/1.9.1/gems/haml-3.0.22/lib/haml/util.rb:459:in `each' /home/slugs/330395_4dc8ceb_905f-8ba444ee-2b55-42da-98ee-04890afc4465/ mnt/.bundle/gems/ruby/1.9.1/gems/haml-3.0.22/lib/haml/util.rb:459:in `each_with_index' /home/slugs/330395_4dc8ceb_905f-8ba444ee-2b55-42da-98ee-04890afc4465/ mnt/.bundle/gems/ruby/1.9.1/gems/haml-3.0.22/lib/haml/util.rb:459:in `check_encoding' /home/slugs/330395_4dc8ceb_905f-8ba444ee-2b55-42da-98ee-04890afc4465/ mnt/.bundle/gems/ruby/1.9.1/gems/haml-3.0.22/lib/haml/util.rb:500:in `check_haml_encoding' /home/slugs/330395_4dc8ceb_905f-8ba444ee-2b55-42da-98ee-04890afc4465/ mnt/.bundle/gems/ruby/1.9.1/gems/haml-3.0.22/lib/haml/engine.rb:90:in `initialize' /home/slugs/330395_4dc8ceb_905f-8ba444ee-2b55-42da-98ee-04890afc4465/ mnt/.bundle/gems/ruby/1.9.1/gems/tilt-1.1/lib/tilt.rb:490:in `new' /home/slugs/330395_4dc8ceb_905f-8ba444ee-2b55-42da-98ee-04890afc4465/ mnt/.bundle/gems/ruby/1.9.1/gems/tilt-1.1/lib/tilt.rb:490:in `prepare' /home/slugs/330395_4dc8ceb_905f-8ba444ee-2b55-42da-98ee-04890afc4465/ mnt/.bundle/gems/ruby/1.9.1/gems/tilt-1.1/lib/tilt.rb:121:in `initialize' /home/slugs/330395_4dc8ceb_905f-8ba444ee-2b55-42da-98ee-04890afc4465/ mnt/.bundle/gems/ruby/1.9.1/gems/sinatra-1.1.0/lib/sinatra/base.rb: 486:in `new' /home/slugs/330395_4dc8ceb_905f-8ba444ee-2b55-42da-98ee-04890afc4465/ mnt/.bundle/gems/ruby/1.9.1/gems/sinatra-1.1.0/lib/sinatra/base.rb: 486:in `block in compile_template' /home/slugs/330395_4dc8ceb_905f-8ba444ee-2b55-42da-98ee-04890afc4465/ mnt/.bundle/gems/ruby/1.9.1/gems/tilt-1.1/lib/tilt.rb:350:in `fetch' /home/slugs/330395_4dc8ceb_905f-8ba444ee-2b55-42da-98ee-04890afc4465/ mnt/.bundle/gems/ruby/1.9.1/gems/sinatra-1.1.0/lib/sinatra/base.rb: 469:in `compile_template' /home/slugs/330395_4dc8ceb_905f-8ba444ee-2b55-42da-98ee-04890afc4465/ mnt/.bundle/gems/ruby/1.9.1/gems/sinatra-1.1.0/lib/sinatra/base.rb: 451:in `render' /home/slugs/330395_4dc8ceb_905f-8ba444ee-2b55-42da-98ee-04890afc4465/ mnt/.bundle/gems/ruby/1.9.1/gems/sinatra-1.1.0/lib/sinatra/base.rb: 370:in `haml' /disk1/home/slugs/ 330395_4dc8ceb_905f-8ba444ee-2b55-42da-98ee-04890afc4465/mnt/ eliason_media.rb:7:in `block in top (required)' /home/slugs/330395_4dc8ceb_905f-8ba444ee-2b55-42da-98ee-04890afc4465/ mnt/.bundle/gems/ruby/1.9.1/gems/sinatra-1.1.0/lib/sinatra/base.rb: 1033:in `call' /home/slugs/330395_4dc8ceb_905f-8ba444ee-2b55-42da-98ee-04890afc4465/ mnt/.bundle/gems/ruby/1.9.1/gems/sinatra-1.1.0/lib/sinatra/base.rb: 1033:in `block in compile!' /home/slugs/330395_4dc8ceb_905f-8ba444ee-2b55-42da-98ee-04890afc4465/ mnt/.bundle/gems/ruby/1.9.1/gems/sinatra-1.1.0/lib/sinatra/base.rb: 620:in `instance_eval' /home/slugs/330395_4dc8ceb_905f-8ba444ee-2b55-42da-98ee-04890afc4465/ mnt/.bundle/gems/ruby/1.9.1/gems/sinatra-1.1.0/lib/sinatra/base.rb: 620:in `route_eval' /home/slugs/330395_4dc8ceb_905f-8ba444ee-2b55-42da-98ee-04890afc4465/ mnt/.bundle/gems/ruby/1.9.1/gems/sinatra-1.1.0/lib/sinatra/base.rb: 604:in `block (2 levels) in route!' /home/slugs/330395_4dc8ceb_905f-8ba444ee-2b55-42da-98ee-04890afc4465/ mnt/.bundle/gems/ruby/1.9.1/gems/sinatra-1.1.0/lib/sinatra/base.rb: 656:in `block in process_route' /home/slugs/330395_4dc8ceb_905f-8ba444ee-2b55-42da-98ee-04890afc4465/ mnt/.bundle/gems/ruby/1.9.1/gems/sinatra-1.1.0/lib/sinatra/base.rb: 653:in `catch' /home/slugs/330395_4dc8ceb_905f-8ba444ee-2b55-42da-98ee-04890afc4465/ mnt/.bundle/gems/ruby/1.9.1/gems/sinatra-1.1.0/lib/sinatra/base.rb: 653:in `process_route' /home/slugs/330395_4dc8ceb_905f-8ba444ee-2b55-42da-98ee-04890afc4465/ mnt/.bundle/gems/ruby/1.9.1/gems/sinatra-1.1.0/lib/sinatra/base.rb: 603:in `block in route!' /home/slugs/330395_4dc8ceb_905f-8ba444ee-2b55-42da-98ee-04890afc4465/ mnt/.bundle/gems/ruby/1.9.1/gems/sinatra-1.1.0/lib/sinatra/base.rb: 602:in `each' /home/slugs/330395_4dc8ceb_905f-8ba444ee-2b55-42da-98ee-04890afc4465/ mnt/.bundle/gems/ruby/1.9.1/gems/sinatra-1.1.0/lib/sinatra/base.rb: 602:in `route!' /home/slugs/330395_4dc8ceb_905f-8ba444ee-2b55-42da-98ee-04890afc4465/ mnt/.bundle/gems/ruby/1.9.1/gems/sinatra-1.1.0/lib/sinatra/base.rb: 741:in `dispatch!' /home/slugs/330395_4dc8ceb_905f-8ba444ee-2b55-42da-98ee-04890afc4465/ mnt/.bundle/gems/ruby/1.9.1/gems
Ruby 1.9.2 and Rails 3.0.1 Support
Does anyone know if there are any limitations on deploying apps on Heroku with MRI 1.9.2 and Rails 3.0.1? Bharat -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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.
ruby 1.9.2
Are there any plans to add a ruby 1.9.2 stack to heroku? It would be nice to build my shiny new rails 3.0 app on ruby 1.9.2 and host it on heroku. I'll be hosting it on heroku either way, but 1.9.2 would be nice. -j -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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.
Re: Ruby 1.9.2
Hi, I remember hearing: We will add support for 1.9.2 when the community releases the official release. But it looks like it will be out soon. http://twitter.com/heroku/status/21517412884 http://blog.heroku.com/archives/2010/6/15/rails_3_beta_4_on_heroku/ --Keenan On Aug 27, 2010, at 10:19 AM, morgoth wrote: ping -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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.
Re: Ruby 1.9.2
ping -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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.
Ruby 1.9.2
So the 1.9.2 is released. When we can expect it on heroku? -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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.
