Hi,
I am about to deploy my first Rails app, but am a little worried about
certain syntax changes from Rails 1.8 to 2.1(which I will be using).
I’m finding it hard to get my head around what happens if the web
hosting company upgrades the Rails version…this will obviously cause
my app to completely and utterly die.
Is there a way to get around this or would I have to purchase a
dedicated server so I know exactly which Rails version I am developing
for.
Thanks for any help. I’ve only been using Rails for two weeks.
Best,
C
On Jul 24, 2:19 am, Clinton Beattie <ruby-forum-incom…@andreas-
s.net> wrote:
I am about to deploy my first Rails app, but am a little worried about
certain syntax changes from Rails 1.8 to 2.1(which I will be using).
I’m finding it hard to get my head around what happens if the web
hosting company upgrades the Rails version…this will obviously cause
my app to completely and utterly die.
Not necessarily. I’ve been able to deploy apps written in Rails 1.2 on
a server running 2.1 with no issues. Most of the issues that are
likely to come up are pretty well documented. (A case where Google is
your friend.)
Is there a way to get around this or would I have to purchase a
dedicated server so I know exactly which Rails version I am developing
for.
This is what freezing is for. If you freeze your version of Rails as
part of your deployment, you can be guaranteed what version of Rails
your app will be running with since the full stack will be included as
part of your application.
–
Alex
Thanks Alex for taking the time to explain all that. I will be looking
into freezing shortly after your heads up.
You should never depend on a shared server gems, basically you are not
in control and a sudden change in them could brake you application.
Try to kee as part of your app any library or gem that you rely on to
avoid this problems.
–
Aníbal Rojas
http://anibal.rojas.com.ve
On Jul 25, 2:09 pm, Clinton Beattie <ruby-forum-incom…@andreas-