Open rdhyee opened 10 years ago
I'm working on a next version of the docs and scripts that addresses that, but thanks for pointing it out. So did it work for you? There are a few assumptions the current version of the script makes and some minor cleanup it needs to do if you don't shut it down cleanly. Nothing should be a showstopper (including the test script, which even if it fails, the proxy itself probably runs fine if you started it up without errors).
I think it worked -- no major complaints/exceptions. It just wasn't obvious to me that the cache is working. (more my own naivete than anything else, perhaps, since I don't have any experience with squid.
-Raymond
On 10/5/14 3:51 PM, Aaron Culich wrote:
I'm working on a next version of the docs and scripts that addresses that, but thanks for pointing it out. So did it work for you? There are a few assumptions the current version of the script makes and some minor cleanup it needs to do if you don't shut it down cleanly. Nothing should be a showstopper (including the test script, which even if it fails, the proxy itself probably runs fine if you started it up without errors).
— Reply to this email directly or view it on GitHub https://github.com/aculich/docker-proxy-cache/issues/2#issuecomment-57955595.
A few other notes about my experience running the cache:
/cache/proxy/squid3
) didn't exist. I ran the command with sudo
but it'd be helpful to say that the cache directory needs to exist before starting the proxy container.squidclient
.
@aculich: on Ubuntu 14.04, I found that I needed to install
squidclient
to run the test:Also, it'd be helpful to document what exactly I should see if we run https://github.com/aculich/docker-proxy-cache/blob/master/test-docker-proxy-cache.sh successfully.