I'm just curious, is there a reason not to use a multi-stage docker build here? There are a ton of build steps, and it seems pretty tedious to have to start from scratch every time while developing the image without any layer caching.
You may find my NGINX image[1] interesting.<p>There's some features you could easily add to yours in order to make it a better overall image.<p>[1] <a href="https://github.com/ricardbejarano/nginx" rel="nofollow">https://github.com/ricardbejarano/nginx</a>
I would suggest highlighting the experimental nature of the repo, especially if someone reaches it without going through HN. I've read the catchy "All built on the bleeding edge. Built on the edge, for the edge." but IMO it doesn't really sound like a warning that this may not be suitable for serious production use.
I did exactly this 3 days ago, forked from fholzer/docker-nginx-brotli our work looks very much the same<p>See <a href="https://github.com/githubcdr/docker-nginx-brotli" rel="nofollow">https://github.com/githubcdr/docker-nginx-brotli</a>
I've played around with the nginx cloudflare patches and quiche, and it all seems to work just fine in my lab setup.<p>I don't like having to apply third party patches to any mission critical software such as nginx. So I'll wait until nginx releases official support for linking the quiche library, like they did with brotli.
This is great, and I'll be using it for development! However, I've been looking for something a bit more predictable, and yet still modern, for production use. I do not know why Brotli support isn't included in every nginx image at this point.
From WP I get the impression that the work-in-progress now called HTTP/3 was not necessarily designed supposed to supplant HTTP/2:<p>> On 28 October 2018 in a mailing list discussion, Mark Nottingham, Chair of the IETF HTTP and QUIC Working Groups, made the official request to rename HTTP-over-QUIC as HTTP/3 to "clearly identify it as another binding of HTTP semantics to the wire protocol ... so people understand its separation from QUIC"<p>Any opinions on how things are likely to play out?
I haven't been following the TLS1.3 development. What is the current state of SNI encryption? Is it possible to encrypt the name of the host you're trying to connect to?