It would be really nice if they had a plain http version of the repo. The reason is, if I include the HTTPS repo in my deployment script, and it's the first time I've run it on a new Debian server, it fails to do an apt-get update because apt-transport-https isn't installed yet.
What with package signing, having an HTTPS repo is kind of pointless.
Comments
It would be really nice if they had a plain http version of the repo. The reason is, if I include the HTTPS repo in my deployment script, and it's the first time I've run it on a new Debian server, it fails to do an apt-get update because apt-transport-https isn't installed yet.
What with package signing, having an HTTPS repo is kind of pointless.
+1. Using HTTP over HTTPS also assists with proxy caching. This can help things like CI run much faster in datacenter environments.
Can't you just create a local APT mirror?
Sure you can, but for the entire archive? Running a caching HTTP proxy is far easier and more lightweight.
So run a caching HTTPS proxy instead?