tazjin

@JohnAZoidberg Thanks, that's close to what I imagined - good to know that this already exists as isolated functionality! The barebones FHS env still pulls in a lot of stuff...

@JohnAZoidberg Are you at NixCon by any chance? If so we could probably spend an hour or so hacking on this.

In general I wouldn't mind adding more "special" packages, but it's unclear how that should be specified in the URL syntax. For example: `/pywithpkgs/requests` -> `python.withPackages (p: [ p.requests ])`...

Docker downloads layers using the `LayerDownloadManager`, implemented in [moby/distribution/xfer/download.go](https://github.com/moby/moby/blob/c9aee96bfd1b456e83807ddd99f06326e1961bc8/distribution/xfer/download.go). The logic in [`Download`](https://github.com/moby/moby/blob/c9aee96bfd1b456e83807ddd99f06326e1961bc8/distribution/xfer/download.go#L99) deals with skipping layers that already exist, but I'm still working my way through it.

This is probably due to https://github.com/moby/moby/issues/38446. My theory is that this is a leftover in Docker from the era before content-addressable image layers, where the order actually mattered.

There does not seem to be a clean way of doing this that works across all Kubernetes clusters using something like `NodePort`. Some discussions with people revealed that there's also...

Exciting times! 

My personal infrastructure repository ([tazjin/depot](https://github.com/tazjin/depot/)) now features a Nixery deployment inside of Kubernetes (see [here](https://github.com/tazjin/depot/tree/master/infra/kubernetes/nixery)). A similar setup to this should be documented in the Nixery docs for people to...

Hey, thanks for this PR! Seems like a useful feature :-) Before doing an in-depth review, I have a couple of remarks: 1. Should both branches and tags be listed?...

Hm, interesting, thanks! Lets spin the tag issue out into a separate problem for now (#89). > Are you suggesting to fetch the repos (HTTP, git://) before running the nix...