From b3946e47d6610cc560f987f1ac3b38d9328e624d Mon Sep 17 00:00:00 2001 From: Tayyip Mert Denizgez Date: Sat, 5 Nov 2022 15:51:32 +0300 Subject: [PATCH] Update running-first-worker.md I believe we should redirect to the backend, not the frontend. At least in my case forwarding the application to the 5000 port which is frontend did not work. --- docs/getting-started/run/running-first-worker.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/getting-started/run/running-first-worker.md b/docs/getting-started/run/running-first-worker.md index 2b1b0b7d..3085703b 100644 --- a/docs/getting-started/run/running-first-worker.md +++ b/docs/getting-started/run/running-first-worker.md @@ -166,7 +166,7 @@ To simplify this tutorial, we have placed the `simple_worker` worker in a [GitHu Clone this repository to your local machine, and open it in your IDE of choice. Our worker will poll the conductor server every second to see if there is a task in it's queue. For that to happen, we need to tell the worker where our Conductor server is. To do this, we must modify the file `/src/main/resources/application.properties`. -* For a local Conductor installation, change `conductor.server.url` to `http://localhost:5000`. +* For a local Conductor installation, change `conductor.server.url` to `http://localhost:8080/api`. * For Playground, you'll need to [create an application](/content/docs/getting-started/concepts/access-control-applications#configuring-your-application) to create a key/secret that authenticates your worker with the playground, and then add the values of the key and secret to lines 2 and 3 of `application.properties` as indicated.