Pete,
My advice is to start from scratch, actually. A custom deployment recipe
is ridiculously easy to write, when you have total control over all the
pieces. For example, it could conceivably just be:
task :deploy do
now = Time.now.to_i
run "cd /path/to/app && git clone repo.url:/app #{now}"
run "ln -nsf /path/to/app/current /path/to/app/#{now}"
end
You don't need 90% of what the standard deployment tasks do. Most of it
is there to support edge cases, and to accommodate people's desires to
try different deployment techniques.
- Jamis
On 1/23/09 6:09 PM, Pete Hodgson wrote:
> Hi Folks,
>
> I have a ruby project that will be going into production soon, and I'd
> love to use capistrano's sweet sweet juju to automate deployment. The
> catch is that this ruby project isn't a rails project. Amazing, I
> know ;) For those that are interested, it's a suite of small discrete
> ruby components that are processing data in parallel, communicating
> via an activeMQ messaging server over stomp. Fun stuff actually!
>
> So my question is, does anyone know of any good resources
> (documentation, wiki articles, blog posts, whatever) on what I'd need
> to do to bend capistrano's will to this task? I've done some research
> and to be honest I haven't found much. I'm assuming most of the work
> here would be in overriding or re-implementing some of the standard
> tasks that cap runs (update_code, rollback etc). Or maybe I'm way off
> target? Anyway, any pointers would be greatly appreciated.
>
> Cheers,
> Pete
> >
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---
