[Radiant] Re: Is there a trick to using Capistrano to deploy Radiant site?

[Errol Siegel]

Must have been some kind of hiccup.  I rebooted, checked out a fresh 
copy of my app from svn, ran capify again, and now it sees all the 
tasks.  Perhaps I did something different, but I can't imagine what it 
would be.  Thanks for the response!
-- 
Posted via http://www.ruby-forum.com/.
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: [Radiant] Re: Is there a trick to using Capistrano to deploy Radiant site?

[Nate Turnage]

On Wed, Oct 1, 2008 at 2:04 PM, Errol Siegel [EMAIL PROTECTED] wrote:

 Must have been some kind of hiccup.  I rebooted, checked out a fresh
 copy of my app from svn, ran capify again, and now it sees all the
 tasks.




Just to veer a little on this, is there a best practices kind of way to use
content versioning with the import_export or super_export extensions?

I have been developing (to a point) on my local machine then putting the
whole app in subversion, cap deploy, rake production, truncate db tables,
then importing a mysql dump from my local machine into the production db.
From there I only do structural changes on my local machine, cap deploy,
then rake any new extensions I added.

Is there a better (read quicker) way to handle content versioning with a
Radiant app?


~Nate
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant