chrisaxiom
commented
8 years ago I'm going to do this now, I need it for timeline - for me I just need to point to say Dockerfile.zest instead of the regular Dockerfile (which will be used for running/testing locally for now, until zest supports integration tests, etc.) Was that a similar use case you had in mind @AndrewBurian ?
The location of the Zestfile will always be the root of the build context sent to docker, but allow overriding the Dockerfile location itself (equivalent to
docker build -f)