You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-functions/durable/durable-task-scheduler/quickstart-durable-task-scheduler.md
+12-38Lines changed: 12 additions & 38 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -72,38 +72,17 @@ Install the latest version of the [Microsoft.Azure.Functions.Worker.Extensions.D
72
72
73
73
::: zone pivot="other"
74
74
75
-
Until the durable task scheduler package is added to the extension bundles, you need to manually install the latest version of these packages using [Azure Functions Core Tools](../../functions-run-local.md#install-the-azure-functions-core-tools):
These commands should automatically generate a *extensions.csproj* file. If the package references aren't added to the file, check to ensure that `net8.0` is the target framework and run the commands again. The file should have content similar to the following example:
@@ -153,23 +132,20 @@ Get the durable task scheduler emulator port number in [the next step](#set-up-d
153
132
1. Run the emulator.
154
133
155
134
```bash
156
-
docker run -itP mcr.microsoft.com/dts/dts-emulator:v0.0.5
135
+
docker run -d -p 8080:8080 -p 8082:8082 mcr.microsoft.com/dts/dts-emulator:v0.0.5
157
136
```
158
137
159
138
The following output indicates the emulator started successfully.
160
139
161
140
:::image type="content" source="media/quickstart-durable-task-scheduler/emulator-started.png" alt-text="Screenshot showing emulator started successfully on terminal.":::
162
141
163
-
1. Make note of the ports exposed on Docker desktop. These static ports are exposed by the container and mapped dynamically by default. The scheduler exposes multiple ports for different purposes:
142
+
1. Make note of the ports exposed on Docker desktop. The scheduler exposes multiple ports for different purposes:
164
143
165
144
-`8080`: gRPC endpoint that allows an app to connect to the scheduler
166
145
-`8082`: Endpoint for durable task scheduler dashboard
167
146
168
147
:::image type="content" source="media/quickstart-durable-task-scheduler/docker-ports.png" alt-text="Screenshot of ports on Docker.":::
169
148
170
-
1. Update the connection string in *local.settings.json* with the gRPC endpoint port number.
171
-
172
-
In the previous example, port `55000` is mapped to the gRPC `8080` endpoint, so the connection string should be `Endpoint=http://localhost:55000;Authentication=None`.
173
149
174
150
## Test locally
175
151
@@ -210,9 +186,7 @@ Get the durable task scheduler emulator port number in [the next step](#set-up-d
210
186
}
211
187
```
212
188
213
-
1. To view more details about the orchestration instance, go to the Docker desktop app and click the `8082` link to access the durable task scheduler dashboard.
214
-
215
-
:::image type="content" source="media/quickstart-durable-task-scheduler/docker-ports.png" alt-text="Screenshot of ports on Docker.":::
189
+
1. To view more details about the orchestration instance, go to **http://localhost:8082/** access the durable task scheduler dashboard.
216
190
217
191
1. Click on the *default* task hub to see its dashboard.
0 commit comments