From d6a86b929511f8dd90c769b9c35e73619ac5f213 Mon Sep 17 00:00:00 2001 From: Tom Gardham-Pallister Date: Wed, 14 Feb 2018 19:01:08 +0000 Subject: [PATCH] +semver: feature --- docs/introduction/gettingstarted.rst | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/introduction/gettingstarted.rst b/docs/introduction/gettingstarted.rst index 8ced66eb..840505f1 100644 --- a/docs/introduction/gettingstarted.rst +++ b/docs/introduction/gettingstarted.rst @@ -68,6 +68,15 @@ AddOcelot() (adds ocelot services), UseOcelot().Wait() (sets up all the Ocelot m } } +AddOcelotBaseUrl +^^^^^^^^^^^^^^^^ + +The most important thing to note here is AddOcelotBaseUrl. Ocelot needs to know the URL it is running under +in order to do Header find & replace and for certain administration configurations. When setting this URL it should be the external URL that clients will see Ocelot running on e.g. If you are running containers Ocelot might run on the url http://123.12.1.1:6543 but has something like nginx in front of it responding on https://api.mybusiness.com. In this case the Ocelot base url should be https://api.mybusiness.com. + +If for some reason you are using containers and do want Ocelot to respond to client on http://123.12.1.1:6543 +then you can do this but if you are deploying multiple Ocelot's you will probably want to pass this on the command line in some kind of script. Hopefully whatever scheduler you are using can pass the IP. + .NET Core 1.0 ^^^^^^^^^^^^^