In the spirit of iterative development I found yet another problem
with this strategy. Cap doesn't like it when a task is executed with
a role/extra information spec that isn't defined. I'm using other
tasks to assign server names to roles (ie. cap production deploy and
cap stage deploy). Some
On Apr 4, 2007, at 9:03 AM, maui wrote:
Hi everyone,
Over here we're using multiple OSs for our rails app. Our dev env is
on a FreeBSD box and we're using TextDrive Accelerators for deployment
(OpenSolaris). As a result we need to customize a few of our tasks
based on the server type.
Very cool!
Thank You Jamis
On Apr 4, 12:51 pm, Jamis Buck [EMAIL PROTECTED] wrote:
On Apr 4, 2007, at 9:03 AM, maui wrote:
Hi everyone,
Over here we're using multiple OSs for our rails app. Our dev env is
on a FreeBSD box and we're using TextDrive Accelerators for deployment
And, _actually_, there's an even better way to do it. (Why do I
always think of these things after opening my mouth?)
The problem with the solution I gave you is that the restarts will
happen serially, instead of in parallel. First, the solaris servers
will restart, and then the others.
A
