Perlbal does manage the health of the web server (which doesn't seem to be the case for nginx, unfortunately). But perlbal doesn't support HTTPS.
Here is a simple perbal.conf file and it nodelist.dat (which you would need to rewrite in case of new app node) *perlbal.conf* # # This is an example webserver configuration. # # See doc/config-guide.txt for descriptions of each command (line) # and configuration syntax. # CREATE POOL dynamic SET nodefile = /etc/perlbal/nodelist.dat CREATE SERVICE balancer SET listen = 0.0.0.0:80 SET role = reverse_proxy SET pool = dynamic SET persist_client = on SET persist_backend = on SET verify_backend = on SET enable_error_retries = on ENABLE balancer # always good to keep an internal management port open: CREATE SERVICE mgmt SET role = management SET listen = 0.0.0.0:60000 ENABLE mgmt *nodelist.dat* (the IP is the internal IP of your node, of course # node1 xx.xx.xx.xx.:port # node2 xx.xx.xx.xx:port --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/scalr-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
