# IPFS for file distribution in local network

**URL:** <https://discuss.ipfs.tech/t/ipfs-for-file-distribution-in-local-network/9458>\
**Category:** Help\
**Created:** [November 17, 2020, 12:47am UTC](https://discuss.ipfs.tech/t/ipfs-for-file-distribution-in-local-network/9458 "2020-11-17T00:47:49Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![wclayf](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/wclayf/32/4936_2.png) [@wclayf](https://discuss.ipfs.tech/u/wclayf)\
**Post date:** [November 17, 2020, 1:53pm UTC](https://discuss.ipfs.tech/t/ipfs-for-file-distribution-in-local-network/9458/5 "2020-11-17T13:53:39Z")

</div>

I’m doing a similar thing where I’m planning to use MFS (Mutable File System) as the backbone for a “federated” platform where each instance on the network will maintain it’s own complete set of certain MFS file structures (directory trees),

I’m _hoping_ that using the MFS Copy command (like below) will have similar behavior to “rsync” insofar as the ability to only copy mostly just changed data when ‘re-syncing’ a across two nodes that are already nearly up to date (as a result of how chunking works). My assumption is that any files that didn’t change at all, for example, would result in zero transfer/storage during the copy operations. I’m hoping to issue just one copy command on the root of the folder structure, and let the ‘recursive’ copy completely to the equivalent of an rsync.

I’m posting here since it is directly related to the above, and may help the OP, but also because I had this question of “am I crazy or not”. to try that. lol. 🙂

```auto
curl -X POST "http://127.0.0.1:5001/api/v0/files/cp?arg=<source>&arg=<dest>"

```

---

_[View the full topic](https://discuss.ipfs.tech/t/ipfs-for-file-distribution-in-local-network/9458)._