# Switch from SVN pull to gem

**URL:** <https://www.ruby-forum.com/t/switch-from-svn-pull-to-gem/147830>\
**Category:** Radiant CMS\
**Created:** [September 5, 2008, 8:20pm UTC](https://www.ruby-forum.com/t/switch-from-svn-pull-to-gem/147830 "2008-09-05T20:20:22Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![glenatron](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/94ad74/32.png) [@glenatron](https://www.ruby-forum.com/u/glenatron)\
**Post date:** [September 5, 2008, 8:20pm UTC](https://www.ruby-forum.com/t/switch-from-svn-pull-to-gem/147830/1 "2008-09-05T20:20:22Z")

</div>

How would I go about switching an established site from a pulled SVN  
installation to using the newest Radiant gem?

Keywords for later searches: update, git, clone

---

<div class="post-metadata">

**Author:** ![glenatron](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/94ad74/32.png) [@glenatron](https://www.ruby-forum.com/u/glenatron)\
**Post date:** [September 5, 2008, 8:31pm UTC](https://www.ruby-forum.com/t/switch-from-svn-pull-to-gem/147830/2 "2008-09-05T20:31:34Z")

</div>

First, unfreeze:

rake radiant:unfreeze

Then install the new gem (and update environment.rb if you have a  
version set in there) and run:

rake radiant:freeze:gem

Sean

---

<div class="post-metadata">

**Author:** ![glenatron](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/94ad74/32.png) [@glenatron](https://www.ruby-forum.com/u/glenatron)\
**Post date:** [September 11, 2008, 8:34am UTC](https://www.ruby-forum.com/t/switch-from-svn-pull-to-gem/147830/3 "2008-09-11T08:34:26Z")

</div>

Tried both

rake radiant:unfreeze | and | rake production radiant:unfreeze

either way I get, “Don’t know how to build task ‘radiant:unfreeze’”

---

<div class="post-metadata">

**Author:** ![glenatron](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/94ad74/32.png) [@glenatron](https://www.ruby-forum.com/u/glenatron)\
**Post date:** [September 11, 2008, 3:01pm UTC](https://www.ruby-forum.com/t/switch-from-svn-pull-to-gem/147830/4 "2008-09-11T15:01:09Z")

</div>

Do you see it in the list of tasks if you execute:

rake -T

–  
John L.  
[http://wiseheartdesign.com](http://wiseheartdesign.com)

---

<div class="post-metadata">

**Author:** ![glenatron](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/94ad74/32.png) [@glenatron](https://www.ruby-forum.com/u/glenatron)\
**Post date:** [September 11, 2008, 5:24pm UTC](https://www.ruby-forum.com/t/switch-from-svn-pull-to-gem/147830/5 "2008-09-11T17:24:34Z")

</div>

It looks like you are running from the source, rather than from the  
gem (or vendor). Is there a reason for that?

---

<div class="post-metadata">

**Author:** ![glenatron](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/94ad74/32.png) [@glenatron](https://www.ruby-forum.com/u/glenatron)\
**Post date:** [September 11, 2008, 5:47pm UTC](https://www.ruby-forum.com/t/switch-from-svn-pull-to-gem/147830/6 "2008-09-11T17:47:48Z")

</div>

Jim G. wrote:

> It looks like you are running from the source, rather than from the  
> gem (or vendor). Is there a reason for that?

When I read the Dreamhost Tutorial, Casper F. suggested running  
from the source because “gems can be troublesome to manage on  
Dreamhost”. However, I don’t think that’s an issue anymore.

---

<div class="post-metadata">

**Author:** ![glenatron](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/94ad74/32.png) [@glenatron](https://www.ruby-forum.com/u/glenatron)\
**Post date:** [September 11, 2008, 5:16pm UTC](https://www.ruby-forum.com/t/switch-from-svn-pull-to-gem/147830/7 "2008-09-11T17:16:40Z")

</div>

Nope, it is not there:

[…]  
rake production # Set the  
environment v…  
rake radiant:clobber\_package # Remove package  
products  
rake radiant:extensions:archive:migrate # Runs the migration  
of…  
rake radiant:extensions:archive:update # Copies public  
assets …  
rake radiant:extensions:gallery:create\_config\_file # Create gallery.yml  
file  
rake radiant:extensions:gallery:install # Migrates and  
copies f…  
rake radiant:extensions:gallery:migrate # Runs the migration  
of…  
rake radiant:extensions:gallery:stats # Report Gallery  
statis…  
rake radiant:extensions:gallery:update # Copies public  
assets …  
rake radiant:extensions:markdown\_filter:migrate # Runs the migration  
of…  
rake radiant:extensions:markdown\_filter:update # Copies public  
assets …  
rake radiant:extensions:page\_attachments:migrate # Runs the migration  
of…  
rake radiant:extensions:reorder:migrate # Runs the migration  
of…  
rake radiant:extensions:reorder:update # Copies public  
assets …  
rake radiant:extensions:update\_all # Runs update asset  
tas…  
rake radiant:gem # Build the gem file  
ra…  
rake radiant:gem:install # Build and install  
Gem…  
rake radiant:gem:uninstall # Uninstall Gem  
rake radiant:package # Build all the  
packages  
rake radiant:release # Publish the  
release f…  
rake radiant:repackage # Force a rebuild of  
th…  
rake rails:freeze:edge # Lock to latest  
Edge R…  
rake rails:freeze:gems # Lock this  
application…  
rake rails:unfreeze # Unlock this  
applicati…  
rake rails:update # Update both  
configs, …  
rake rails:update:configs # Update  
config/boot.rb…  
[…]

I’m running 0.6.7… ?

John W. Long wrote:

> Do you see it in the list of tasks if you execute:
> 
> rake -T
> 
> –  
> John L.  
> [http://wiseheartdesign.com](http://wiseheartdesign.com)

---

<div class="post-metadata">

**Author:** ![glenatron](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/94ad74/32.png) [@glenatron](https://www.ruby-forum.com/u/glenatron)\
**Post date:** [September 12, 2008, 5:58am UTC](https://www.ruby-forum.com/t/switch-from-svn-pull-to-gem/147830/8 "2008-09-12T05:58:30Z")

</div>

Jim G. wrote:

> Try running it from vendor instead.
> 
> That will make a copy of the radiant source in my\_site/vendor/radiant  
> And just incase you are wondering, Rails is bundled in my\_site/vendor/  
> radiant/vendor/rails

I need the 0.6.7 gem installed to do that, right? I’ll need to keep  
everything (files, database) I’ve created so far.

---

<div class="post-metadata">

**Author:** ![glenatron](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/94ad74/32.png) [@glenatron](https://www.ruby-forum.com/u/glenatron)\
**Post date:** [September 11, 2008, 7:16pm UTC](https://www.ruby-forum.com/t/switch-from-svn-pull-to-gem/147830/9 "2008-09-11T19:16:25Z")

</div>

On Sep 11, 2008, at 11:47 AM, Ben M. wrote:

> Jim G. wrote:
> 
> > It looks like you are running from the source, rather than from the  
> > gem (or vendor). Is there a reason for that?
> 
> When I read the Dreamhost Tutorial, Casper F. suggested running  
> from the source because “gems can be troublesome to manage on  
> Dreamhost”. However, I don’t think that’s an issue anymore.

Try running it from vendor instead.

You can create an instance of radiant with  
‘radiant my\_site’  
‘cd my\_site’  
‘rake radiant:freeze:gems’

That will make a copy of the radiant source in my\_site/vendor/radiant  
And just incase you are wondering, Rails is bundled in my\_site/vendor/  
radiant/vendor/rails

That would allow you to ‘unfreeze’ later, or even do  
‘radiant:freeze:edge’ to get new features that haven’t made it into an  
official release yet.

---

<div class="post-metadata">

**Author:** ![glenatron](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/94ad74/32.png) [@glenatron](https://www.ruby-forum.com/u/glenatron)\
**Post date:** [September 12, 2008, 3:44pm UTC](https://www.ruby-forum.com/t/switch-from-svn-pull-to-gem/147830/10 "2008-09-12T15:44:33Z")

</div>

On Sep 11, 2008, at 11:58 PM, Ben M. wrote:

> Jim G. wrote:
> 
> > Try running it from vendor instead.
> > 
> > That will make a copy of the radiant source in my\_site/vendor/radiant  
> > And just incase you are wondering, Rails is bundled in my\_site/  
> > vendor/  
> > radiant/vendor/rails
> 
> I need the 0.6.7 gem installed to do that, right? I’ll need to keep  
> everything (files, database) I’ve created so far.

Yes.  
You’d need to move anything that you added or altered into the  
directory of your new app. This includes your config/database.yml,  
environment file changes, public, and anything in vendor/extensions  
(or vendor plugins if you added anything to the default)
