# Rails Versions

**URL:** <https://www.ruby-forum.com/t/rails-versions/121927>\
**Category:** Radiant CMS\
**Created:** [December 2, 2007, 11:57pm UTC](https://www.ruby-forum.com/t/rails-versions/121927 "2007-12-02T23:57:25Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![james-calivar](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/2bfe46/32.png) [@james-calivar](https://www.ruby-forum.com/u/james-calivar)\
**Post date:** [December 2, 2007, 11:57pm UTC](https://www.ruby-forum.com/t/rails-versions/121927/1 "2007-12-02T23:57:25Z")

</div>

Do I need to freeze my radiant site on a shared host. I have read that  
Radiant ties itself to a certain version of rails. How does this work,  
and how will it be affected when the host deletes that gem and installs  
a newer version? Also, what if I need to move to a newer version of  
rails to get security fixes?

---

<div class="post-metadata">

**Author:** ![james-calivar](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/2bfe46/32.png) [@james-calivar](https://www.ruby-forum.com/u/james-calivar)\
**Post date:** [December 3, 2007, 12:07am UTC](https://www.ruby-forum.com/t/rails-versions/121927/2 "2007-12-03T00:07:43Z")

</div>

Radiant ties itself to Rails by inclusion (look in  
vendor/radiant/vendor/rails, or gems/radiant-0.6.x/vendor/rails). Both  
frozen and gem Radiant ignores any Rails gems you have installed.

As far as moving to a newer version of Rails for security fixes, the  
core team tries to keep on top of that. 0.6.5 will include Rails 1.2.6,  
which came out after the Radiant 0.6.4 release. Since Rails 2 will be  
out soon, 0.6.6 will probably include Rails 2.x.

Sean

---

<div class="post-metadata">

**Author:** ![james-calivar](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/2bfe46/32.png) [@james-calivar](https://www.ruby-forum.com/u/james-calivar)\
**Post date:** [December 3, 2007, 12:10am UTC](https://www.ruby-forum.com/t/rails-versions/121927/3 "2007-12-03T00:10:38Z")

</div>

> Do I need to freeze my radiant site on a shared host. I have read that  
> Radiant ties itself to a certain version of rails. How does  
> this work,  
> and how will it be affected when the host deletes that gem  
> and installs  
> a newer version? Also, what if I need to move to a newer version of  
> rails to get security fixes?

Radiant supplies rails in it’s vendor directory - the gem install on  
your  
shared host should be completely ignored.

If you need a different version of rails for security fixes, you can  
freeze radiant and switch out the rails implementation:

rake radiant:freeze:gem

and then replace vendor/radiant/vendor/rails with the version of rails  
you  
want.

But if it’s a security thing, probably best to just tell us and we’ll  
upgrade our rails and re-release to suit (most of the core team have  
customers paying using radiant and will jump on any security issues  
quick-smart).

Dan.

---

<div class="post-metadata">

**Author:** ![james-calivar](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/2bfe46/32.png) [@james-calivar](https://www.ruby-forum.com/u/james-calivar)\
**Post date:** [December 3, 2007, 12:16am UTC](https://www.ruby-forum.com/t/rails-versions/121927/4 "2007-12-03T00:16:01Z")

</div>

OK. Thanks for the help. I wanted to be sure that my site (also for a  
customer) would not be affected by updates unless wanted.