Skip to content

Commit 2cd1f39

Browse files
author
hastmu
committed
first release
1 parent ac85e0f commit 2cd1f39

File tree

2 files changed

+29
-2
lines changed

2 files changed

+29
-2
lines changed

README.md

Lines changed: 28 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -49,4 +49,31 @@ Reading state information... Done
4949

5050
# How to install?
5151

52-
will follow next days...
52+
So the quickest way is:
53+
```
54+
dev@dev:~$ curl -s https://raw.githubusercontent.com/hastmu/apt-proxy-detect/main/install.sh | sudo bash
55+
- check dependencies...
56+
- download latest to: /usr/local/bin/apt-proxy-detect.sh
57+
- set permissions to a+rx
58+
- create/updating /etc/apt/apt.conf.d/30apt-proxy-detect.conf
59+
60+
```
61+
62+
or you just download the install.sh and run it locally.
63+
64+
# How does it work?
65+
66+
The apt.conf.d entry makes apt aware of the tool which is then call during "apt update",
67+
for some reason most of the other tools are not aware that you get the target URL as
68+
parameter for this call.
69+
70+
This URL is the proxy check URL to confirm that the found or cached proxy is working with
71+
this dedicated URL as some proxies may have white/black lists or just not got configured
72+
right or outdated for the new stuff to be checked out.
73+
74+
In case a proxy is not serving the URL it is drop for this dedicated URL.
75+
76+
The found (via avahi-browse _apt_proxy._tcp) proxies are cached under /tmp/.apt-proxy.<username>
77+
in case this has the wrong owner it is ignored and a waring is issued.
78+
79+
Thats it. Enjoy.

apt-proxy-detect.sh

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
#!/bin/bash
22

3-
# (c)opyright by hastmu@gmx.net
3+
# (c)opyright by gh-hastmu@gmx.de
44
# checkout https://github.com/hastmu/apt-proxy-detect
55
# v1 ... pure detect
66
# v2 ... cache value with check

0 commit comments

Comments
 (0)