rylin wrote:
snip/
Given the example-tree:
A
-1
--I
-2
B
-3
I might only need to deploy I and 3 (e.g., I don't need the
contents of the entire tree, just the contents of I and 3).
I'm guessing I'll have to start hacking a new update_code task, but
I've no real idea on where to
On Jan 23, 2007, at 2:13 AM, jeroen wrote:
Hi Jamis,
It sure is helpful info. However it doesn't completely answer my
question. My question is more like: how can I can I make sure the
:repository var *only* changes when I do a deploy or
deploy_with_migrations?
What about update_code? You
On 1/23/07, NeilW [EMAIL PROTECTED] wrote:
Ezra,
I appreciate that the method_missing idea has a certain appeal to it,
but does it really save that much time for the aggravation it might
cause?
I don't see a vast saving between
sh.rm_rf fred
and
sh.rm -rf fred
Particularly when
On Jan 22, 2007, at 10:02 PM, Ezra Zygmuntowicz wrote:
So I have worked on this some more to incorporate being abel to set
ENV vars per line if you want.
sh.RAILS_ENV('production').mkdir_p 'foo/bar'
#= RAILS_ENV=production mkdir -p foo/bar
Nice!
Jamis asked me to get the
The cached repository enhancement may also be worth looking at. It does
one checkout to the shared dir and rsyncs updates to the current
folder. You could modify it to take extra variables corresponding to
the parts of the repository that you are deploying.
http://pastie.caboo.se/24849
Jamis Buck wrote:
On Jan 23, 2007, at 2:13 AM, jeroen wrote:
Hi Jamis,
It sure is helpful info. However it doesn't completely answer my
question. My question is more like: how can I can I make sure the
:repository var *only* changes when I do a deploy or
deploy_with_migrations?
I've got a plugin working which decouples deployment from the SCM in
use. It currently supports only Subversion (I'll be emailing the
maintainers of the other Capistrano SCM modules to work with them on
that), but it supports FIVE different deployment strategies (well,
only three really,
On Jan 23, 2007, at 2:42 PM, S. Robert James wrote:
I would suggest to versions of cached_repository:
1. Incremental.
2. Clean (rm -rf and sync everything from the beginning).
Could you elaborate on the difference between these?
(On Perforce, this would be p4 sync and rm -rf p4 sync
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 bit would be
