The code is Cap 2.2 based so alot of things need to be updated.
Unfortunately I had to code some "hacks" at the time because cap 2.2
didnt support a number of things that are now in 2.4. The newer 2.4 +
cap versions would greatly reduce alot of junk that I have in my code.
I will talk with the customer about a release cycle.

On Sep 26, 5:22 am, "Gaveen Prabhasara" <[EMAIL PROTECTED]>
wrote:
> +1
>
> It'll be really interesting to see. Shadowbq, can we keep hopes up? :)
>
> -Gav
>
> On Fri, Sep 26, 2008 at 2:29 AM, Jamis Buck <[EMAIL PROTECTED]> wrote:
>
> > Cool stuff! I'd love to see a write-up of this. Would be neat to point
> > people at it as an example of capistrano "beyond rails", as it were.
>
> > - Jamis
>
> > On Sep 25, 2008, at 2:31 PM, shadowbq wrote:
>
> > > I use capistrano for managing an entire Intrusion Detection Sensor
> > > fleet that has NOTHING to do with Rails. I have capistrano called from
> > > within ruby files not utilizing the "cap"command. Ive used for over a
> > > year to manage all aspects of binary sensor deployment, full BSD
> > > buildouts, svn repo configuration management, daily log rotations, I
> > > have ruby apps utilizing capistrano libraries to output to syslog
> > > reporting to monitor equipment. Capistrano is super flexible and with
> > > an open mind can be utilized for Lots of stuff!
>
> > > I wrote an entire monitor/trusted software application around
> > > capistrano libraries because I cant trust output from binaries on the
> > > target networks.
>
> > > On Sep 23, 11:40 am, mzgubin <[EMAIL PROTECTED]> wrote:
> > >> Can capistrano be used for doing deployments of things other than
> > >> Ruby/
> > >> Rails?
> > >> Can it be used to deploy Java WAR files or random files like assets
> > >> etc?
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---

Reply via email to