News for hackers. Stuff that matters.

A comment on HTTPS-Portal: Automated HTTPS server powered by Nginx, Let’s Encrypt and Docker. Parent comment

Re:HTTPS-Portal: Automated HTTPS server powered by Nginx, Le... by Rowern on Friday September 14, 2018 @04:19AM (#17985568)
Traefik is really cool for most usage, I tried to used it in production and here are some of the shortcoming I found (the 2 first issues are on github):

- If you use DNS for a blue-green deployment, traefik does not honor DNS ttls (because it uses the DNS of go and go might do some caching) so when you do the switch you might still end on the "old" environment

- An error on one of the cool feature: serving error page when your backend returns some HTTP code

- Some configuration options are not documented (but easily found using github search)

I still love this software and I will keep looking at it.

[ Parent | on HN ]
Re:HTTPS-Portal: Automated HTTPS server powered by Nginx, Le... by dward on Friday September 14, 2018 @11:01AM (#17987649)
By default, go compiles binaries linked to libc to use the system DNS resolver. It does re-implement a DNS resolver but it's only used if CGO is disabled at compilation time.
[ Parent | on HN ]
Re:HTTPS-Portal: Automated HTTPS server powered by Nginx, Le... by axaxs on Friday September 14, 2018 @01:41PM (#17989201)
That's only half right. It does link to libc, but the default behavior on linux is to use Go unless some conditions are met.
[ Parent | on HN ]
Re:HTTPS-Portal: Automated HTTPS server powered by Nginx, Le... by dward on Wednesday September 26, 2018 @03:46PM (#18079576)
Use go for what? DNS resolution? The default behavior is to use the system DNS resolver. The Go resolver will be used if the system is resolver is not avaialble (e.g. if the binary is compiled as pure go) or if the net.Resolver has the PreferGo flag set (which is false by default).

https://github.com/golang/go/blob/541f9c0345d4ec52d9f4be5913...

[ Parent | on HN ]