Upgrade tyk2.0 from older version, Also want to setup in docker

[Carlos_Carvalho]

@Martin

if Tyk detects two listen paths that are a string match, it will skip the latter, so a wildcard might not help here.

What are you trying to achieve? No matter what yu do you will need to differentiate an inbound request by org somehow, that’s either busy path or by domain…

I’m trying to have the same API in a multi tenant setup. I have a nginx that will balance the incoming requests for this API and redirect to tyk gateway upstream…I need to redirect to the correspondent “tenant API”

Example:

 ORG 1 Path 1
 /api/tenant1

 API Definition 1
 /api/{tenant1}


 ORG 2 Path 2
 /api/tenant2


API D1finition 2
 /api/{tenant2}