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 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
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.
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.