# Rsync

**URL:** <https://forum.ansible.com/t/rsync/11488>\
**Category:** Ansible Project\
**Created:** [May 2, 2012, 10:56am UTC](https://forum.ansible.com/t/rsync/11488 "2012-05-02T10:56:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Samuele\_Tognini](https://avatars.discourse-cdn.com/v4/letter/s/22d042/32.png) [@Samuele\_Tognini](https://forum.ansible.com/u/Samuele_Tognini)\
**Post date:** [May 2, 2012, 10:56am UTC](https://forum.ansible.com/t/rsync/11488/1 "2012-05-02T10:56:37Z")

</div>

Hi all,  
Are there plans to extend the git module to make use of rsync to deploy software?  
It think that the old way to push files from the master to nodes (and execute handlers when something has changed) sometimes could be still useful.

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan](https://avatars.discourse-cdn.com/v4/letter/m/c4cdca/32.png) [@Michael\_DeHaan](https://forum.ansible.com/u/Michael_DeHaan)\
**Post date:** [May 2, 2012, 11:28am UTC](https://forum.ansible.com/t/rsync/11488/2 "2012-05-02T11:28:55Z")

</div>

This is pretty much a no.

Various concerns:

(A) The git module is intended to be well tuned to git, so it’s not a good fit

and more importantly

(B) Rsync wouldn’t really be using paramiko, so it would be fine if using authorized\_keys, but various handling with accounts and sudo would be more or less impossible.

Some sort of recursive copy support for the copy module (src=directory, dest=directory, include\_pattern=?), however, is doable.

Someone would need to submit a batch to the copy code in runner.py to support this.