Hi Jerome, Thank you for replying.. I appreciate the detailed response and being patient for my beginner's questions :)
Also, I want to apologise as I seems my last message was sent a couple of times :P I'm very excited with my shift to Linux and very happy about VirtualRails.. and no doubt it's worth it ;) Since I think any projects I started on Windows should now anyway be re-written on Linux (also since I'm planning to deploy on a linux host, which was mainly what made me shift at this point of time to Linux.. but it was anyway just a matter of time till I do move.. just made things quicker..) - I'll begin using rails 2.3.8 :) Glad nokogiri not updating successfully is not going to cause me any problems, and right now I'm not using it anyway, though it seems nice after doing some reading.. about environment.rb - I realised this is where I should mention the rails version.. but thanks for mentioning it and validating what I thought.. same goes for my virtualrails' home directory, it really helped me you answered this very basic question for me :) Many thanks and thank you for your VirtualRails project. Best, tino On Jul 7, 3:53 pm, Jerome Fillioux <[email protected]> wrote: > Hi Tino, > I think your problems are simple than you think :) > > first, don't bother upgrading successfully nokogiri until you really > need to > use it in your project. and don't worry about the failed update, on > won't > have any side effect. > > about the rails version, there is only one thing to consider IMO : > - if you start a new rails application, use the last "stable" > version, > i.e 2.3.8 : less bugs, more speed, more security. > - if you work on an existing rails app, use the rails version that has > been > used to create and developp this application. Until you have a real good > reason to migrate your app to a newer version of rails, don't :) > > one interessant thing you have to know is that you can have several > rails > versions installed on your system, and choose the one to use in the > configuration file of your rails project. In the > /config/environnement.rb > file, add somthing like that : > # Specifies gem version of Rails to use when vendor/rails is not present > RAILS_GEM_VERSION = '2.3.5' unless defined? RAILS_GEM_VERSION > > regarding all this, I think you can stay with your original snapshop, > and > choose the rails version you want to use. > but you can also use a fresh downloaded virtualrails and upgrade only > rails > if you want, it takes only 5 minutes and you will be more confortable > with > the idea that only rails have been upgraded :) > > about the place you should put your files, your right : > the "/home/virtualrails/" is like the "My Documents" for MS Windows, > "virtualrails" being the name of the connected user. > for exemple you can create a folder named "rails_apps" or "dev", or > what > you want under the "/home/virtualrails/" directory, and put here all > your > future rails projects. > > cheers up, > keep learning Linux and Rails, it really worth the price :) > > Jérôme Fillioux > VirtualBox Team > -- > Posted viahttp://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
