Roxxy is a distributed HTTP/websockets reverse proxy backed by Redis inspired by planb and hipache

• Load-Balancing

• Dead Backend Detection

• Dynamic Configuration

• WebSocket

• TLS

The easiest way to install Roxxy Proxy is to pull the build from the Github Container Registry and launch it in the container:

# run Redis

docker run -d -p 6379:6379 redis

# run Roxxy
docker run -d --net=host ghcr.io/aaqaishtyaq/roxxy --listen ":80"

The configuration is managed by Redis that makes possible to update the configuration dynamically and gracefully while the server is running, and have that state shared across workers and even across instances.

Let's take an example to proxify requests to 2 backends for the hostname www.aaqa.dev. The 2 backends IP are 10.10.0.2 and 10.10.0.3 and they serve the HTTP traffic on the port 80.

redis-cli is the standard client tool to talk to Redis from the terminal.

Follow these steps:

$ redis-cli rpush frontend:www.aaqa.dev mywebsite
(integer) 1

The frontend identifer is mywebsite, it could be anything.

$ redis-cli rpush frontend:www.aaqa.dev http://10.10.0.2:80
(integer) 2
$ redis-cli rpush frontend:www.aaqa.dev http://10.10.0.3:80
(integer) 3

$ redis-cli lrange frontend:www.aaqa.dev 0 -1
1) "mywebsite"
2) "http://10.10.0.2:80"
3) "http://10.10.0.3:80"

redis-cli -x hmset tls:www.aaqa.dev certificate < server.crt
redis-cli -x hmset tls:www.aaqa.dev key < server.key

redis-cli -x hmset tls:*.tsuru.com certificate < wildcard.crt
redis-cli -x hmset tls:*.tsuru.io key < wildcard.key

create directory following this structure

cd certficates
ls
*.domain-wildcard.com.key
*.domain-wildcard.com.crt
absolute-domain.key
absolute-domain.crt

While the server is running, any of these steps can be re-run without messing up with the traffic.

The following flags are available for configuring Roxxy on start-up: