Is there a trick to using Capistrano to deploy Radiant site?

Ruby Apps Radiant CMS
1

I installed the capistrano gem and ran capify . (after first adding
/var/lib/gems/1.8/bin to the PATH variable).

When I try cap deploy:setup I get:

the task `deploy:setup’ does not exist

I have not run into this problem trying to use Capistrano with regular
rails apps.

Is there something special I need to do?

2

On Sep 30, 2008, at 6:28 PM, Errol S. wrote:

Is there something special I need to do?
No special tricks.

Is there anything different about your environment than with your
regular rails apps? You mentioned that you had to install the gem, so
I assume that this is some other environment.
What do you get with “which cap”

3

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!

4

On Wed, Oct 1, 2008 at 2:04 PM, Errol S. [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

5

Nate:

Good question. In fact, I have another thread going (should be right
near this one) where I am trying to sort out best practices for this
sort of thing.

I also am playing with the import_export plugin (and running into some
issues). I’ll post the details on the other thread shortly.

There are a couple of obvious issues to deal with when developing a site
like this locally:

  1. Syncing databases.
  2. Syncing data files. For example, page_attachments stores files in a
    subdirectory of public.
  3. Syncing program files. For example, I use a few custom extensions
    and I want to develop them locally. I figure Capistrano is a no-brainer
    for this third requirement, and that seems to be working pretty well so
    far.