Nicolas Steinmetz writes:
> > My other concern is that I would like that all actions are written to a
> log
> > file so that I can audit if a deployment went well or not.
>
> Your assumption that output currently only goes to stdout/stderr, is
> correct -- however, there are p
On Wed, Feb 10, 2010 at 3:54 PM, Nicolas Steinmetz wrote:
> For now, I have a commands.upd file which can contains commands to execute
> against some servers :
> Ex :
> remote front cd /var/www/myapp && php path/to/script.php -s : will
> execute the given command on all frontals
> remote once fr
On Wed, Feb 10, 2010 at 11:54 PM, Nicolas Steinmetz
wrote:
> Hi,
>
> 2010/2/10 Jeff Forcier
>>
>> Could you provide an example here? I'm afraid I don't quite follow
>> what you're asking :)
>
> Yep, of course :-)
> For now, I have a commands.upd file which can contains commands to execute
> again
Hi,
2010/2/10 Jeff Forcier
> Hi Nicolas,
>
> On Wed, Feb 10, 2010 at 11:32 AM, Nicolas Steinmetz
> wrote:
> >
> > For complex deployment, i may need to run extra commandes like run some
> > scripts on one or serveral frontal servers or on a given db.
> >
> > I would like to avoid providing a ne
Hi Nicolas,
On Wed, Feb 10, 2010 at 11:32 AM, Nicolas Steinmetz
wrote:
>
> For complex deployment, i may need to run extra commandes like run some
> scripts on one or serveral frontal servers or on a given db.
>
> I would like to avoid providing a new fabfile and was looking for taking
> into acc
Hi,
Back to fabric, I rewrote yesterday my perl deployment tool in fabric.
So far, I handle the basic use case "simple deployment".
I have other UC to implement :
- backup (quite easy)
- complex deployment
For complex deployment, i may need to run extra commandes like run some
scripts on
