# Is a Local Deb mirror worth it?

**URL:** <https://community.learnlinux.tv/t/is-a-local-deb-mirror-worth-it/3696>\
**Category:** Homelab\
**Created:** [March 16, 2024, 4:52am UTC](https://community.learnlinux.tv/t/is-a-local-deb-mirror-worth-it/3696 "2024-03-16T04:52:32Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Witenite](https://community.learnlinux.tv/letter_avatar_proxy/v4/letter/w/4bbf92/32.png) [@Witenite](https://community.learnlinux.tv/u/Witenite)\
**Post date:** [March 16, 2024, 4:52am UTC](https://community.learnlinux.tv/t/is-a-local-deb-mirror-worth-it/3696/1 "2024-03-16T04:52:32Z")

</div>

I am building out my home lab with multiple Debian VM’s. I am wondering if there is a good reason to have a local Deb mirror or have all my Debian systems pull from an official mirror.

I have an ISP with 1500/150 and no data caps.

Thoughts?

---

<div class="post-metadata">

**Author:** ![ThatGuyB](https://community.learnlinux.tv/user_avatar/community.learnlinux.tv/thatguyb/32/784_2.png) [@ThatGuyB](https://community.learnlinux.tv/u/ThatGuyB)\
**Post date:** [March 16, 2024, 2:27pm UTC](https://community.learnlinux.tv/t/is-a-local-deb-mirror-worth-it/3696/2 "2024-03-16T14:27:55Z")

</div>

Unless you have a few hundred to a thousand, no. A repo can be 1 TB+ in size, which you need to keep synced. If you only have a handful or even a few dozen, not worth it.

Most major distros discourage you build your own repo, unless you have insane amounts of VMs. Debian does recommend you use a community mirror closest to you, to save on the bandwidth used on the main repo.

---

<div class="post-metadata">

**Author:** ![Witenite](https://community.learnlinux.tv/letter_avatar_proxy/v4/letter/w/4bbf92/32.png) [@Witenite](https://community.learnlinux.tv/u/Witenite)\
**Post date:** [March 16, 2024, 2:59pm UTC](https://community.learnlinux.tv/t/is-a-local-deb-mirror-worth-it/3696/3 "2024-03-16T14:59:43Z")

</div>

Thank you. I could see both sides. Official mirrors it is.

---

<div class="post-metadata">

**Author:** ![ThatGuyB](https://community.learnlinux.tv/user_avatar/community.learnlinux.tv/thatguyb/32/784_2.png) [@ThatGuyB](https://community.learnlinux.tv/u/ThatGuyB)\
**Post date:** [March 16, 2024, 5:33pm UTC](https://community.learnlinux.tv/t/is-a-local-deb-mirror-worth-it/3696/4 "2024-03-16T17:33:06Z")

</div>

What you can do is configure a squid-proxy and enable caching. When you do update for one system (if you use the http\_proxy and https\_proxy variables, I don’t remember if they’re all lower-case or all upper-case), you cache the data, then for the rest of the systems, the cache will be partially used (depending on the deb packages downloaded).

---

<div class="post-metadata">

**Author:** ![node](https://community.learnlinux.tv/user_avatar/community.learnlinux.tv/node/32/1214_2.png) [@node](https://community.learnlinux.tv/u/node)\
**Post date:** [May 5, 2024, 4:14pm UTC](https://community.learnlinux.tv/t/is-a-local-deb-mirror-worth-it/3696/5 "2024-05-05T16:14:52Z")

</div>

I think I am going to try this. Thanks!