Ruby Forum Radiant CMS > Switch from SVN pull to gem

Posted by Ben Morrow (benmorrow)
on 05.09.2008 20:20
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
Posted by Sean Cribbs (seancribbs)
on 05.09.2008 20:31
(Received via mailing list)
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
Posted by Ben Morrow (benmorrow)
on 11.09.2008 08:34
Tried both

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

either way I get, "Don't know how to build task 'radiant:unfreeze'"

Posted by John W. Long (Guest)
on 11.09.2008 15:01
(Received via mailing list)
Do you see it in the list of tasks if you execute:

   rake -T

--
John Long
http://wiseheartdesign.com
Posted by Ben Morrow (benmorrow)
on 11.09.2008 17:16
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 Long
> http://wiseheartdesign.com
Posted by Jim Gay (Guest)
on 11.09.2008 17:24
(Received via mailing list)
It looks like you are running from the source, rather than from the
gem (or vendor). Is there a reason for that?
Posted by Ben Morrow (benmorrow)
on 11.09.2008 17:47
Jim Gay 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 Fabricius suggested running 
from the source because "gems can be troublesome to manage on 
Dreamhost". However, I don't think that's an issue anymore.
Posted by Jim Gay (Guest)
on 11.09.2008 19:16
(Received via mailing list)
On Sep 11, 2008, at 11:47 AM, Ben Morrow wrote:

> Jim Gay 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 Fabricius 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.
Posted by Ben Morrow (benmorrow)
on 12.09.2008 05:58
Jim Gay 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.
Posted by Jim Gay (Guest)
on 12.09.2008 15:44
(Received via mailing list)
On Sep 11, 2008, at 11:58 PM, Ben Morrow wrote:

> Jim Gay 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)