On Jan 7, 2007, at 9:06 PM, Charles Brian Quinn wrote:
For a client, we altered the repository line to read:
set :repository,
https://svn.server.com/#{application}/tags/#{ENV['DEPLOY_VERSION']}
so now it is deployed with:
cap deploy DEPLOY_VERSION=1.2.5
hope that helps
On 1/7/07,
Hi all,
The title says it all: I'd like 'deploy', or another custom-made task,
to create an entry in a feed.
The simpler to implement, the better.
Contents:
- In its simplest form, I'd already be happy with just an entry (no
content)
- Additionaly, placing the revision number somewhere (title
On 1/8/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Hi all,
The title says it all: I'd like 'deploy', or another custom-made task,
to create an entry in a feed.
The simpler to implement, the better.
Contents:
- In its simplest form, I'd already be happy with just an entry (no
content)
-
Hi Wolfmans,
thank you very much for the solution, I will go ahead and use/test it
and let you know how it goes.
I am not sure if this is what you've meant, but my plan is to have one
development server that has access to perforce, have this server update
itself from the repository, then have
Capistrano requires, or at least expects, that each deployment target
machine performs a checkout of source code. In the examples provided,
the machine does this by checking out from a development machine, if I
understand correctly.
This seems less than ideal because it requires that a
On Jan 8, 2007, at 6:51 PM, [EMAIL PROTECTED] wrote:
Has anyone configured capistrano such that code is always pushed
to, and
never pulled by, the deployment target machines? How did you do it?
KM,
Have a peek at the list archives, there has been quite a bit of
discussion about this
