# Docker Flow Proxy [![GitHub release](https://img.shields.io/github/release/docker-flow/docker-flow-proxy.svg)]() [![license](https://img.shields.io/github/license/docker-flow/docker-flow-proxy.svg)]() [![Docker Pulls](https://img.shields.io/docker/pulls/vfarcic/docker-flow-proxy.svg)]() [![Go Report Card](https://goreportcard.com/badge/github.com/docker-flow/docker-flow-proxy)](https://goreportcard.com/report/github.com/docker-flow/docker-flow-proxy) The goal of the *Docker Flow Proxy* project is to provide an easy way to reconfigure proxy every time a new service is deployed, or when a service is scaled. It does not try to "reinvent the wheel", but to leverage the existing leaders and combine them through an easy to use integration. It uses [HAProxy](http://www.haproxy.org/) as a proxy and adds custom logic that allows on-demand reconfiguration. Supported architectures are: - linux-amd64 - linux-arm Please visit the **[project documentation](docs/index.md)** for more info or join the #df-proxy Slack channel in [DevOps20](http://slack.devops20toolkit.com/) if you have any questions, suggestions, or problems. Buy Me a Coffee at ko-fi.com