Flexworks Site Config Builder for openresty/nginx

Introduction

Having multiple versions/stacks of the same website, they need to know about the config and so does the reverse proxy, which connects you to any of these backends. Not wanting to duplicate config, storing it in a single json file as the single source of truth seems pretty convincing. An app will be built to manage this config and we needed something to translate this json into an nginx importable config. That's where this project comes in.

execute

binary

./flexsitecfg --config config.json --output nginx.upstream.conf

run code

dotnet run -- --config config.json --output nginx.upstream.conf

• mind the intentional --, it's there for a reason (terminate dotnet command and start cli arguments for flexsitecfg)

example

input

{
    "backend_id1": {
        "description": "first backend",
        "backend_servers": [
            {
                "servername": "192.168.1.1",
                "port": 8080
            }
        ]
    },
    "backend_id2": {
        "description": "another backend",
        "backend_servers": [
            {
                "servername": "192.168.1.3",
                "port": 4040
            }
        ]
    }
}

output

# first backend
upstream backend_id1 {
    server 192.168.1.1:8080;
}

# another backend
upstream backend_id2 {
    server 192.168.1.3:4040;
}

upstream backend_servers {
    server 192.168.1.1:8080 max_fails=3 fail_timeout=30s;
    server 192.168.1.3:4040 max_fails=3 fail_timeout=30s;
}

build

 dotnet publish -c Release -r osx-arm64 --self-contained true /p:PublishSingleFile=true /p:EnableCompressionInSingleFile=true

(can't use /p:PublishTrimmed=true without explicitly managing the json types in code)