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
Typically when installing Dapr in self-hosted mode, a Placement service container is added to Docker exposing the default port 6500. If this samle is run
17
+
Typically when installing Dapr in self-hosted mode, a Placement service container is added to Docker exposing the default port 6050. If this same is run
18
18
while that container is up it will be unable to start due to a port conflict. Instead a different port 6501 is assigned to Placement in configuration:
19
19
20
20
```json5
@@ -30,7 +30,7 @@ unless a specific remote address is defined. For example the following specifies
This sample shows how Dapr Sidekick can be used to host the Dapr Scheduler service alongside a Dapr Sidecar instance. Sidekick will launch the Scheduler service and wait for it
4
+
to enter a healthy running state, then will launch the Sidecar alongside. The Sidecar will be configured to use the launched Scheduler service by default.
5
+
As with the Sidecar, the Scheduler service will be continually monitored and maintained for the lifetime of the application.
6
+
7
+
## How Dapr Sidekick was added
8
+
9
+
This is an ASP.NET Core minimal Web API project. Dapr Sidekick was added to the [Program.cs](SchedulerSample\Program.cs) file as follows:
Typically when installing Dapr in self-hosted mode, a Scheduler service container is added to Docker exposing the default port 6060. If this same is run
18
+
while that container is up it will be unable to start due to a port conflict. Instead a different port 6061 is assigned to Scheduler in configuration:
19
+
20
+
```json5
21
+
"Scheduler": {
22
+
"RuntimeDirectory":"scheduler",
23
+
"Id":"dapr-scheduler-server-0", // Optional unique identifier when used in a cluster
24
+
"Port":6061// To avoid conflicts with local Dapr Scheduler container. Sidecar will use this automatically as well.
25
+
}
26
+
```
27
+
28
+
By default the Sidecar that is launched alongside the Scheduler service will look for the Scheduler service locally on this custom port,
29
+
unless a specific remote address is defined. For example the following specifies a three-host remote Scheduler cluster:
0 commit comments