On Aug 15, 11:12 am, "Anthony Ettinger" <ettin...@gmail.com
> Are there any good references of what the freeze process is used for, and why?
$ rake -D rails:freeze:edge
Lock to latest Edge Rails, for a specific release use
$ rake -D rails:freeze:gems
Lock this application to the current gems (by unpacking them into
If you have have in your development box different rails applications
tied to different rails versions you will need to freeze so each
application uses the freezed rails version under vendor/rails folder.
If you don't have control on what rails gems are installed you should
not take chances and freeze rails before ever thinking on deploying.
> I found the Deployment book to fall a little short on freezing.
> I've tried freezing, and it appears to have deleted everything in the
> path, when I do an svn update, I get it all back.
Please add more info here.
> Also, the architecture of deployment with respect to ruby (and also
> rails) independtly.
These are two different things,it would be unusual having trouble with
your Ruby version.
> I'm a little confused on where the framework lives, is the Rails
> version I use part of my deployment, or is that provided by the ISP on
> their server?
When a Rails based applications initializes it can use a a specific
Rails version available as a gem, or use the same libraries located
> I'm pretty sure I'm stuck with whatever ruby version they install,
> unless I install my own.
if you are not running your own VPS or Dedicated Server, I would not
recommend trying to install your own Ruby version, it requires
building from source, fixing paths for the build and setting up
environment variables, it is possible, but it is a lot of work if you
don't have the skills.