Happened to see this while looking through recent posts and figured what the heck. I went for very simple with the standard library, a Dockerfile, and no tests. Threw them up as a gist.
+1 for how you use Go Docker image and Docker stages to build project! I see this build in stage pattern being more and more popular for cloud native applications. It makes total sense for me!
BTW Is there any reason to set up GOPROXY? I guess it defaults to https://proxy.golang.org anyway?
Happened to see this while looking through recent posts and figured what the heck. I went for very simple with the standard library, a Dockerfile, and no tests. Threw them up as a gist.
gist.github.com/shindakun/4ebd21c2...
Thank you Steve! I love it.
+1 for how you use Go Docker image and Docker stages to build project! I see this build in stage pattern being more and more popular for cloud native applications. It makes total sense for me!
BTW Is there any reason to set up
GOPROXY? I guess it defaults tohttps://proxy.golang.organyway?PS I will try to comment more later!
Thanks! The
GOPROXYis really just left over from and older revision, it does not need to be in there any longer as far as I know.Hey Steve :) , Why did you use docker in this task, could we just use go run ? Thanks !