Do people really announce new releases just over email and things like mail-archive or? Those mail archives always looked strange to me for some unknown reason.
If there is a mailing list for the software, why not send releases information over there? It makes a lot of sense to me. I'm also subscribed to several, and some software also announce patches or security related stuff on mail lists. I see mail as a low barrier of entry (every developer has an email address). What else would you use to notify interested people and be able to receive feedback at the same time?
HAProxy 1.8.0
11–20 of 24 posts
Re: HAProxy 1.8.0
#12We use it on many of our projects and it has always been a very reliable piece of software, even at high traffic.
Kudos Willy and team, congratulations on the release!
-b
Re: HAProxy 1.8.0
#13Now I know what my week R&D time will be : HTTP2 in HAProxy !
Re: HAProxy 1.8.0
#14Do people really announce new releases just over email and things like mail-archive or? Those mail archives always looked strange to me for some unknown reason.
Re: HAProxy 1.8.0
#15I really am amazed at the stability and quality of the HAProxy project and that since it's inception many , many years ago. We use it on many of our projects and it has always been a very reliable piece of software, even at high traffic. Kudos Willy and team, congratulations on the release! -b
Re: HAProxy 1.8.0
#16Otherwise, outside of SSL, HAProxy has been very pleasant in my experience.
Re: HAProxy 1.8.0
#17I do hope that HAProxy might support ACME at some point, I'm currently stuck on Traefik which has been breaking some traffic but I rely heavily on dynamically issued LE certs. Otherwise, outside of SSL, HAProxy has been very pleasant in my experience.
frontend http_in
bind *:80
bind *:443 ssl crt /path/to/letsencrypt/data/mydomain.pem
acl path_letsencrypt path_beg /.well-known/acme-challenge
use_backend letsencrypt if path_letsencrypt
backend letsencrypt
mode http
server server-letsencrypt MYLOCALIP:8080
For the letsencrypt docker image, I use mesosphere/letsencrypt-dcos with a patched run.sh that triggers a docker kill -s HUP on the haproxy container.Re: HAProxy 1.8.0
#18I do hope that HAProxy might support ACME at some point, I'm currently stuck on Traefik which has been breaking some traffic but I rely heavily on dynamically issued LE certs. Otherwise, outside of SSL, HAProxy has been very pleasant in my experience.
Where's your problem? Spin up a certbot docker container and use this here in haproxy: frontend http_in bind *:80 bind *:443 ssl crt /path/to/letsencrypt/data/mydomain.pem acl path_letsencrypt path_beg /.well-known/acme-challenge use_backend letsencrypt if path_letsencrypt backend letsencrypt mode http server server-letsencrypt MYLOCALIP:8080 For the letsencrypt docker image, I use mesosphere/letsencrypt-dcos with a…
If I, for example, configure my PHP VM to be reachable over "test.example.org" in Traefik, then Traefik will automatically try to issue a certificate for this domain once it detects the config change.
On HAProxy this is not as easy as I need to tell both LE and HAP about the new backend.
If it was integrated, I would only have to tell HAP.
Re: HAProxy 1.8.0
#19I do hope that HAProxy might support ACME at some point, I'm currently stuck on Traefik which has been breaking some traffic but I rely heavily on dynamically issued LE certs. Otherwise, outside of SSL, HAProxy has been very pleasant in my experience.
Re: HAProxy 1.8.0
#20I do hope that HAProxy might support ACME at some point, I'm currently stuck on Traefik which has been breaking some traffic but I rely heavily on dynamically issued LE certs. Otherwise, outside of SSL, HAProxy has been very pleasant in my experience.
Can you share your experience with Traefik? We also wanted to integrate it into our stack. What problems do you have? How it scales?
It also lacks support for HTTP streaming for non-standard HTTP (I wish there was an option to just enable streaming on a host) which sucks for some enterprise software, and streaming for entire hosts so my nextcloud instance always has to wait for the traefik host to buffer the response before being able to download the file to the browser.
However, in terms of scaling and being able to get a SSL-terminating or SSL-handover reverse proxy going it's a breeze and it handles decent load very well.