Closed mhils closed 8 years ago
you'll need to do some tweaks to the docker hub to have it use the branches/tags going forward, can make those changes over @ https://hub.docker.com/r/mitmproxy/releases/~/settings/automated-builds/
Yes, thanks @dweinstein! :smiley: I think we can just keep the old versions on Dockerhub as-is and start with a single 0.17 branch. If noone objects, I'll try that out tomorrow.
SGTM
This PR replaces the
mitmproxy/docker-releases
repo contents with a single revised Dockerfile that tracks git master. As proposed by @wernight in https://github.com/mitmproxy/docker-base/pull/5, our modus operandi would be to create a separate branch for each release, in which we update requirements.txt. As a next step, we can then get rid of the docker-base repository to simplify things.@cortesi, @dweinstein, @wernight, are you ok with this? I'd love to have quick progress here because I need this for another project I'm working on.