Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
home_server:home_server_setup:other_services:aptcache [2019-12-21 Sat wk51 14:56] – [Set Up and Ubuntu APT Cache] baumkphome_server:home_server_setup:other_services:aptcache [2023-04-30 Sun wk17 17:43] (current) – external edit 127.0.0.1
Line 1: Line 1:
-{{tag>Apt cache apt-cacher-ng}}+{{tag>linux ubuntu debian Apt cache apt-cacher-ng apt update apt upgrade apt-get}}
 =====Set Up and Ubuntu APT Cache===== =====Set Up and Ubuntu APT Cache=====
  
Line 16: Line 16:
   *The default cache directory is: ''/var/cache/apt-cacher-ng'' and can be changed in the configuration file.   *The default cache directory is: ''/var/cache/apt-cacher-ng'' and can be changed in the configuration file.
   *The default log directory is: ''/var/log/apt-cacher-ng'' and can be changed in the configuration file.   *The default log directory is: ''/var/log/apt-cacher-ng'' and can be changed in the configuration file.
-  *The clients can access apt-cacher-ng cache by adding the following line into the new file: ''sudo vim /etc/apt/apt.conf.d/02proxy'',+  *The clients can access apt-cacher-ng cache by adding the following line into the new file: ''sudo vim /etc/apt/apt.conf.d/02proxy'', also check ''sudo vim /etc/apt/apt.conf.d/00aptproxy'':
     *''%%Acquire::http::Proxy "http://192.168.1.1:3142";%%''     *''%%Acquire::http::Proxy "http://192.168.1.1:3142";%%''
  
 There is an issue with use of apt-cacher and SSL/TLS repositories. A good reference is from packagecloud:blog: [[https://blog.packagecloud.io/eng/2015/05/05/using-apt-cacher-ng-with-ssl-tls/|Using apt-cacher-ng with SSL/TLS]].  The apt-cacher-ng manual section 8.3 [[https://www.unix-ag.uni-kl.de/~bloch/acng/html/howtos.html#ssluse|8.3 Access to SSL/TLS remotes (HTTPS)]] is source reference.  The general clients access noted above "''sudo vim /etc/apt/apt.conf.d/02proxy'', ''%%Acquire::http::Proxy "http://192.168.1.1:3142";%%''" will not function with https secured repositories.  Instead each repository will need to be manual set as http to apt-cache-ng with aptchahe-ng accessing the https repositories and caching them locally.  When performing a ''sudo apt update'' note the repository errors and find the repository within repository files in the sub-directory ''/etc/apt''.  Below is some I have found: There is an issue with use of apt-cacher and SSL/TLS repositories. A good reference is from packagecloud:blog: [[https://blog.packagecloud.io/eng/2015/05/05/using-apt-cacher-ng-with-ssl-tls/|Using apt-cacher-ng with SSL/TLS]].  The apt-cacher-ng manual section 8.3 [[https://www.unix-ag.uni-kl.de/~bloch/acng/html/howtos.html#ssluse|8.3 Access to SSL/TLS remotes (HTTPS)]] is source reference.  The general clients access noted above "''sudo vim /etc/apt/apt.conf.d/02proxy'', ''%%Acquire::http::Proxy "http://192.168.1.1:3142";%%''" will not function with https secured repositories.  Instead each repository will need to be manual set as http to apt-cache-ng with aptchahe-ng accessing the https repositories and caching them locally.  When performing a ''sudo apt update'' note the repository errors and find the repository within repository files in the sub-directory ''/etc/apt''.  Below is some I have found:
-  *''sudo vim /etc/apt/sources.list.d/nodesource.list'' +  *''sudo vim /etc/apt/sources.list.d/nodesource.list''; change: 
-    *change ''deb https://deb.nodesource.com/node_10.x bionic main'' to ''deb http://https///deb.nodesource.com/node_10.x bionic main +    *''%%deb https://deb.nodesource.com/node_10.x bionic main%%'' to ''deb %%http://https///deb.nodesource.com/node_10.x bionic main%%'' 
-'' +    *''%%deb-src https://deb.nodesource.com/node_10.x bionic main%%''to ''%%deb-src http://https///deb.nodesource.com/node_10.x bionic main%%''
----- +
-===Home Server Index=== +
-++++Home Server Index|<pagelist&header> +
-*[[home_server:home_server_setup:summary]] +
-*[[home_server:home_server_setup:home_it_setup]] +
-*[[home_server:home_server_setup:Network_setup]] +
-*[[home_server:home_server_setup:kvm]] +
-*[[home_server:home_server_setup:vnc_setup]] +
-*[[home_server:home_server_setup:disk_check]] +
-*[[home_server:home_server_setup:other_services]] +
-</pagelist>+++++
  
-===Home Server Other Index=== +For ''sudo do-release-upgrade''  change ''sudo vim /etc/update-manager/meta-release'' 
-++++Home Server Other Index|<pagelist&header> + 
-*[[home_server:home_server_setup:other_services:index]] +----
-*[[home_server:home_server_setup:other_services:timedate]] +
-*[[home_server:home_server_setup:other_services:aptcache]] +
-*[[home_server:home_server_setup:other_services:swap]] +
-*[[home_server:home_server_setup:other_services:bash]] +
-*[[home_server:home_server_setup:other_services:vim]] +
-*[[home_server:home_server_setup:other_services:symlinks]] +
-*[[home_server:home_server_setup:other_services:fail2ban]] +
-*[[home_server:home_server_setup:other_services:monit]] +
-*[[home_server:home_server_setup:other_services:tripwire]] +
-*[[home_server:home_server_setup:other_services:misc]] +
-</pagelist>+++++
  
 <- home_server:home_server_setup:other_services:timedate|Prev ^ home_server:home_server_setup:other_services:index|Start page ^ home_server:home_server_setup:other_services:swap|Next -> <- home_server:home_server_setup:other_services:timedate|Prev ^ home_server:home_server_setup:other_services:index|Start page ^ home_server:home_server_setup:other_services:swap|Next ->