Reed Allman

meant with `iron_worker_ng`, sorry. that's why I had him try this thing out. he had some good feedback, said that he wanted a simple "hello world" tutorial for upload and...

ah. think he meant quick and easy zip. we could add a zip to that guy

that's not a bad idea either. I just meant as a tutorial a simple `hello_world.zip` laying around somewhere for people to say "hello world"

This needs to be updated for modules and get rid of the GOPATH lingo, reminding myself to at least update the README instructions. now we can probably crawl up to...

yea this is more of a convenience, none of this is defaulted or required. we do require setting scope to run a refactoring, I'm mostly referring to updating https://github.com/godoctor/godoctor.vim/#setting-scope-to-git-root in...

we support multiple registries configured in `~/.docker/config` or through `DOCKER_AUTH` env var in fn. i am less sure if it works properly, but there was an attempt. it should be...

thanks for details. yeah, I buy that. am having trouble reproducing locally. fix doesn't seem straightforward, for detached we probably shouldn't be handing over the same response writer that we're...

i've got a possible fix, working on it at least. i need to read the detached stuff again to be sure.

thanks, I follow and agree about the logger. from what I can tell, this means that TryExec itself needs to be handed a response writer that is safe for writing...

agree about not doing concurrent safe respwriter, yea. that option sounds the best to me, I was trying to figure out where to do this. TryExec seems just fine. PlaceCall...