Remove load balancer proxy for Web (maybe)

[lorenjohnson]

I am ALMOST certain we can remove the lb1.hylo.com proxy and it won’t change anything on Web:

• We need to double-check the Haproxy config on that instance, and confirm again we understand everything that is happening there. While it is a load balancing setup we only have one instance of our backend configured and in actuality, so it is not currently actually doing any load balancing. It is/was however potentially service the purpose of mitigating some issue with cookies-based auth for our Sails WebSockets setup as per a link to this in a a comment at that top of that config file: https://www.exratione.com/2012/12/websockets-over-ssl-haproxy-nodejs-nginx

• If in the above analysis it is clear that the proxy is no longer needed for proper WebSocket auth/functioning, and no other purpose for the proxy is found, then we should switch it off. All that is needed to do that is change the DNS entry for www.hylo.com to point to Heroku and no longer be a CNAME to lb1.hylo.com, then turn-off the Droplet after saving snapshot for backup.

• Another option which runs the risk of some disruption in production is to simply change the DNS entries and test carefully to make sure everything works ok.