Pros and cons running local repository (for packages like deb, rpm etc)?
-
What are the pros and cons running a local mirror/repository?
In my case for debian and primarily for servers but it would be the same for clients and regardless if you use deb or rpm packages etc.
Pros I'm thinking are less internet bandwidth and higher speed when running updates and installs. And that you can limit internet access to servers that doesn't need it. And that you can put several external repositories into one local (I think).
Cons would be storage space - amd64 repository for debian stable is around 60 GB. And the hassle to run it.
I already have local "repository" for instance for iso images - I assume everyone does.
What do you think? Yea or ney?
-
I had to do it the last place I worked because we were air gapped. With RPMs it's pretty easy. I can see the value if you are updating a lot of systems on a small pipe. If you deploy from templates/are immutable I don't see the value.
-
@Pete-S said in Pros and cons running local repository (for packages like deb, rpm etc)?:
Cons would be storage space - amd64 repository for debian stable is around 60 GB.
According to the information in this link, which is updated daily, amd64 is 330 GB.
https://www.debian.org/mirror/size -
@black3dynamite said in Pros and cons running local repository (for packages like deb, rpm etc)?:
@Pete-S said in Pros and cons running local repository (for packages like deb, rpm etc)?:
Cons would be storage space - amd64 repository for debian stable is around 60 GB.
According to the information in this link, which is updated daily, amd64 is 330 GB.
https://www.debian.org/mirror/sizeIt's because that includes everything like testing, unstable, experimental and what not. Also source code. So it's a couple of different versions of the OS.
The amd64 stable main contrib non-free are 60.1 GB today - as of right now...
