James B. Byrne wrote: > > On Tue, November 20, 2012 06:53, C. L. Martinez wrote: >> On Tue, Nov 20, 2012 at 11:23 AM, Phil Dobbin <bukowskiscat at gmail.com> >> wrote: >>> On 11/20/2012 08:39 AM, C. L. Martinez wrote: >>>> >>>> Somebody knows if exists some rpm package for ruby rails?? >>> Normally, rubygems is the way to go to install Rails. >> >> Sure, but how can I update rubygems installed in one system?? > > The main problem with RHEL and Ruby on Rails is that the version of > Ruby available for EL6 from reputable repositories is too old. RoR > 3.2 can get by on 1.8.7 but support for Ruby versions prior to 1.9.3 > is being dropped in the forthcoming RoR v4 release. Thus, a > RHEL/CentOS rpm package for Rails really will not give you much, if > anything. > > I suggest that you investigate both RBENV and RVM as alternatives to > using the rpm packaged Ruby. I advise you consider that for RoR > projects the Bundler gem is the preferred way of installing and > managing project specific packages, including Rails itself. > > The down side to this approach is that your production servers need to > have development tools installed to build the Ruby interpreter and the > support gems. The up side is that you can version specific ruby vms > and gemsets on a project by project basis. > > https://github.com/sstephenson/rbenv > https://rvm.io/ > http://gembundler.com/ > > I used rvm almost from its inception but have recently changed to > rbenv as this has a much smaller footprint on the user's environment. > But both are excellent products. If you are installing RoR for a > production environment then you will almost certainly need to consider > using Passenger (mod-rails) as well. > > https://www.phusionpassenger.com/ Here, they use Ruby, the enterprise version - is that what you mean by RBENV or RVM? The next release of ruby? from RH? will be the 1.93 or some such, and include all the stuff in the enterprise version. Development tools on a production box are a very, VERY bad idea. I assume you can build the ruby app on your development box, and then move it as a package to test, then prod. I've also seen an article or two about ruby not scaling up well. From my experience here, the apps seem to be *very* fragile, and it reminds me of python 10-12 years ago, where updating it one or two subreleases broke everything that had been working, including system tools. ObStmt: No, I don't like ruby. mark