Displaying 1 to 20 from 28 results

patroni - A template for PostgreSQL High Availability with ZooKeeper, etcd, or Consul


You can find a version of this documentation that is searchable and also easier to navigate at patroni.readthedocs.io.There are many ways to run high availability with PostgreSQL; for a list, see the PostgreSQL Documentation.

fabio - A fast, modern, zero-conf load balancing HTTP(S) router for deploying microservices managed by consul


fabio is a fast, modern, zero-conf load balancing HTTP(S) and TCP router for deploying applications managed by consul.Register your services in consul, provide a health check and fabio will start routing traffic to them. No configuration required. Deployment, upgrading and refactoring has never been easier. It integrates with Consul, Vault, Amazon ELB, Amazon API Gateway and more.

voyager - ✈️️ Secure Ingress Controller for Kubernetes


Voyager is a HAProxy backed secure L7 and L4 ingress controller for Kubernetes developed by AppsCode. This can be used with any Kubernetes cloud providers including aws, gce, gke, azure, acs. This can also be used with bare metal Kubernetes clusters.Voyager provides L7 and L4 loadbalancing using a custom Kubernetes Ingress resource. This is built on top of the HAProxy to support high availability, sticky sessions, name and path-based virtual hosting. This also support configurable application ports with all the options available in a standard Kubernetes Ingress. Here is a complex ingress example that shows how various features can be used. You can find the generated HAProxy Configuration here.

rotating-proxy - Rotating TOR proxy with Docker


Why: Lots of IP addresses. One single endpoint for your client. Load-balancing by HAproxy.Please note: Tor offers a SOCKS Proxy only. In order to allow communication from HAproxy to Tor, Polipo is used to translate from HTTP proxy to SOCKS proxy. HAproxy is able to talk to HTTP proxies only.




haproxy_exporter - Simple server that scrapes HAProxy stats and exports them via HTTP for Prometheus consumption


This is a simple server that scrapes HAProxy stats and exports them via HTTP for Prometheus consumption.For more information check the source code documentation. All of the core developers are accessible via the Prometheus Developers mailinglist.

farm - haproxy + stud made easy, socket.io ready


Provides means to scale HTTP/HTTPS servers in unobtrusive way. Uses haproxy as reverse proxy and load balancer for HTTP, and stud as HTTPS terminator. Supports socket.io. Serves permissive Flash Sockets Policy. Now you have haproxy listening to :80 for HTTP and :65443 for HTTPS terminated by stud listening to :443.

haproxy-with-letsencrypt-auto-renewal - HAProxy with letsencrypt auto renewal


This container contains an HAProxy server with an auto Letsencrypt renewal service.

mikoi - mikoi is a HAProxy's proxy protocol enabler for command line tools.


mikoi is a HAProxy's proxy protocol enabler for command line tools. It is designed to work to monitor ProxyProtocol enabled server with usual monitoring plugins such as nagios-plugins and sensu-plugins.


haproxy - HAProxy management and orchestration


HAProxy is an amazing proxy, it has support for many different algorithms for load balancing, it can handle HTTP, TCP, WebSocket connects, does SSL termination and much much more. But managing these proxies can be a bit of a pain. That's where haproxy comes in, it provides a access to the stat socket of HAProxy which allows you to enable, disable servers and front-ends, read out stats and much more. In addition to that it's also capable of hot reloading configuration changes and starting, stopping your HAProxy, even when it's running as a daemon. In order to make your HAProxy installation work with this module you need to expose the stats socket interface of HAProxy. If you don't have this specified in your configuration please add the following to the global section of your configuration.

haminer - Library and program to parse and forward HAProxy logs


Library and program to parse and forward HAProxy logs. This steps assume that you already installed Go, git, gometalinter, and influxdb.

archi_cloudnative - Cloud Native Architectural Models using Archi


Cloud Native Architectural Models using Archi. Contains models for CAAS, Cloud Native Applications, 12/15 Factor Applications with CI/CD/CS, monitoring and log management. Infrastructure components include Red Hat OpenShift, Red Hat Storage, Red Hat Cloudforms, Red Hat JBoss Java Web Server, Red Hat JBoss Enterprise Application Server, Red Hat JBoss Business Rules Management, Red Hat JBoss Data Grid, Red Hat JBoss Data Virtualization and Red Hat Ansible. Includes material and architectural thinking from the following books. The Archi® modelling tool is targeted toward all levels of Enterprise Architects and Modellers. It provides a low cost to entry solution to users who may be making their first steps in the ArchiMate modelling language, or who are looking for a free, cross-platform ArchiMate modelling tool for their company or institution and wish to engage with the language within a TOGAF® or other Enterprise Architecture framework.

ansible-role-haproxy - Ansible Role - HAProxy


Installs HAProxy on RedHat/CentOS and Debian/Ubuntu Linux servers. Note: This role officially supports HAProxy versions 1.4 or 1.5. Future versions may require some rework.

consul-haproxy-example - HAProxy load balancing Node.js apps discovered via Consul


This project will show how to dynamically instantiate Node.js application processes and have Consul reconfigure and restart HAProxy. Each of these programs consist of a single binary. You can choose to install them completely or simply download and execute the binary. If doing the latter be sure to adjust relative paths.

upbeat - Fast health and performance checking


Upbeat is a high performance node-based healthcheck/dashboard. Upbeat allows you to run health checks and provides a dashboard to chart the performance. It also allows you to proxy and cache these health checks so they don't tax your system. You can now reduces the number of health checks to a service from O(N) to O(1). Services are a way of grouping several sensor checks together. In the example above, we have a "google" service w hich we check by making a get request to "http://www.google.com" and also seeing if we have a connection to port 8 0 on the "google.com" host. In the yaml config, a service is a "hash" of sensors where the keys are the names of the sensors and the values are the configuration.

proxymatic - Marathon service discovery proxy


The proxymatic image forms one part of a network level service discovery solution. It dynamically configures proxies that forward network connections to the host where a service is currently running. By subscribing to events from discovery sources such as Marathon or registrator the proxies can quickly be updated whenever a service is scaled or fails over. Given a Marathon URL, proxymatic will fetch the running tasks and configure proxies that forward connections from the servicePort to the host and port exposed by the task. Proxymatic subscribes to the Marathon event bus and receive cluster changes immediately when they occur, which cuts the response time in case of failover or scaling.

varnishtraining - Second iteration of my Varnish training


This repository contains the example code for the 6-hour Varnish training I created. This is the second iteration of the training course and was first presented at Symfony Live Berlin 2017.

haproxy-auth-request - auth-request allows you to add access control to your HTTP services based on a subrequest to a configured haproxy backend


auth-request allows you to add access control to your HTTP services based on a subrequest to a configured haproxy backend. The workings of this Lua script are loosely based on the ngx_http_auth_request_module module for nginx. The Lua script will make a HTTP request to the first server in the given backend that is not marked as DOWN. This allows for basic health checking of the auth-request backend. If you need more complex processing of the request forward the auth-request to a separate haproxy frontend that performs the required modifications to the request and response.