I'll second this advice. I may not know enough about your needs, but with a CMS, it doesn't seem importance what version of Rails or Ruby a CMS runs on, since a full-blown app is not what Radiant CMS is designed for. And with RVM, it's easy to admin a server with multiple versions of Ruby and Rails to accommodate different projects with different version needs running on the same server.
More important, IMO, is how well documented each CMS is or (perhaps better) how easy it is to get help from other developers, including contractors (lots and lots of good developers are fluent in Radiant and are available to help). I'm not one of them although I've created several Radiant CMS sites, and it's very easy once you do one, but I'm not familiar with developing complex applications in Radiant. It's more difficult when you try to create a complex app but at that point a straight Rails project is a better choice. But I've been told that a Rails app can be written and included into a Radiant site as a plugin, although I haven't done that (yet). Kevin On Aug 7, 2011, at 7:30 AM, Bob Sleys wrote: > I know everyone like to use the latest and greatest versions of software and > all but IMHO I don't think its a good idea to limit an evaluation of CMS to > specific build versions of ruby or rails. Instead it would be far better to > make sure they are being actively developed and have a good solid team behind > them. For something you want to be able to depend on often you don't want > the latest and greatest, cutting edge version, but something that you know > will work, has a good team behind it and well supported by a community of > users where you can get questions answered. > > Bob
