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_migr
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?
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?
Just out of interest, I noticed that capistrano has a lot in common
with rake,
Jeroen,
You can use lazily evaluated variables to make sure the work only
happens when it absolutely needs to happen. Something like this:
set :repository do
# do all your work here, and make sure the block
# returns the value you want the repository variable
# to take.
en
