ftest creates a Docker network called ftest and runs job containers on it. Job containers upload results back to the ftest server. This should work fine, when ftest server is running as a container and is part of the container network. But when developing or when using the (WIP) CLI tool, this isn't feasible.

So this simple nginx proxy configuration exists to expose ftest server running on port 29130 on host machine to the ftest network.