I'm very much looking forward to that. I'm already using Capistrano to
deploy PHP apps as well as my RoR apps. I can only expect the direction
of Cap2 will make it easier to do more and more of our deployments with Cap.
Thanks in advance,
--R
Jamis Buck wrote:
> My vision for Capistrano 2.0
On Jan 23, 2007, at 2:47 PM, S. Robert James wrote:
> Jamis Buck wrote:
>> My vision for Capistrano 2.0 is to follow the suggestions a few
>> people have offered and decouple "Capistrano-the-part-that-executes-
>> remote-processes" from "Capistrano-does-rails-deployment". The "core"
>> capistrano
Jamis Buck wrote:
> My vision for Capistrano 2.0 is to follow the suggestions a few
> people have offered and decouple "Capistrano-the-part-that-executes-
> remote-processes" from "Capistrano-does-rails-deployment". The "core"
> capistrano bit would be installable standalone, with no defaults. Th
Neil,
My vision for Capistrano 2.0 is to follow the suggestions a few
people have offered and decouple "Capistrano-the-part-that-executes-
remote-processes" from "Capistrano-does-rails-deployment". The "core"
capistrano bit would be installable standalone, with no defaults. The
rails-spec
Very nice, Mike. I've committed it. Thanks!
- Jamis
On Jan 17, 2007, at 1:23 AM, Mike Bailey wrote:
I tracked down the source of a problem today related to
overriding :restart in .caprc.
As of Capistrano 1.3.0 you cannot override standard tasks
from .caprc because it is
loaded before the
How does '-x' work with this lot?
It would be quite useful if '-x' skipped preloading of any task library
- including standard. I might be (and often am!) doing something with
capistrano that doesn't involve Rails deployment at all.
--~--~-~--~~~---~--~~
To unsu
