Yep, exactly.
I would probably do something like making the path the git module include
the version number in the destination path {{ version }}
and that way you wouldn't have to do a live update on the code existing
code tree.
(General disclaimer -- Many folks would use a load balancer instead for
this purpose, as not all applications can deal with simply swapping out the
code directory and must require service restarts. Of course, for those
that can, this is great)
On Fri, Dec 27, 2013 at 9:49 AM, Brian Coca <[email protected]> wrote:
> no but easy to implement with ansible:
>
> - action: whatever you need to deploy code to release specific dir
> (git/copy/unarchive/etc)
>
> - file: path=/procuduction/link src=/path/you/just/deployed/to
>
> - service: name=appserver state=reloaded|restarted
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ansible Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> For more options, visit https://groups.google.com/groups/opt_out.
>
--
Michael DeHaan <[email protected]>
CTO, AnsibleWorks, Inc.
http://www.ansibleworks.com/
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
