Creates a local .deb cache that can be connected to.

Useful for low bandwidth environments, or those who nuke their system (TINKER!)

My basic setup is:

Separate drive/partition from /

Need to modify:

#store at location
/etc/apt-cacher-ng/acng.conf needs to edit path to storage.

#give permissions to apt-cacher-ng user (default user service)
chmod -R 2755 /storage/location
chown -R apt-cacher-ng:apt-cacher:ng /storage/location

#tell apt to use this proxy
nano -w /etc/apt/apt.conf.d/02proxy

acquire::http::proxy "http://localhost:3142";

(other machines would point to IP address of apt-cacher-ng server)

Basically, when you enable this proxy setting with this service, whatever machine connects through it, host machine will download update list and when you update programs, will cache it locally so when it is queried, you can achieve LAN speed updates.

Might hack on this later, just wanted to get the idea out for anyone who feels like playing.

I am using Apt-Cache NG for all debian based SBCs, because most of them have no need for internet access and with that not allowed to.
Now my question is how apt-cacher ng would work while each dietpi system checks with dietpi if I use one local machine being the apt-cache NG Server?

Example: Raspberry Pi3 with dietpi has not internet access and cannot check for updates, I would do that manually as it is the typical sudo apt update.