Allow TCP backend to be configured

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Workhorse needs to be able to talk to gitlab-rails (Unicorn). Currently we have two ways of doing that:

• with TCP at http://localhost:8080
• with Unix sockets at a configurable socket path

What's missing here is connecting to gitlab-rails with TCP at an arbitrary address. We may want this for cloud-native deployments. cc @marin