I've had rare cases of needing nested data structures in the environment. My solution was to specify them as JSON strings and load the value in code. It works.

    USER='{
        "name": "joe",
        "email":"joe@example.com"
    }'

Indeed, I only had "simple" cases in mind. But hey... shouldn't the complex config files paths be specified through env vars ? ;)