Merge pull request #3170 from hhunter-ms/issue_3169

Link to multi-app run quickstarts

daprdocs/content/en/developing-applications/local-development/multi-app-dapr-run/multi-app-overview.md

@@ -82,4 +82,5 @@ Watch [this video for an overview on Multi-App Run](https://youtu.be/s1p9MNl4VGo
 
 ## Next steps
 
-[Learn the Multi-App Run template file structure and its properties]({{< ref multi-app-template.md >}})
+- [Learn the Multi-App Run template file structure and its properties]({{< ref multi-app-template.md >}})
+- [Try out the Multi-App Run template with the Service Invocation quickstart]({{< ref serviceinvocation-quickstart.md >}})

daprdocs/content/en/getting-started/quickstarts/serviceinvocation-quickstart.md

@@ -107,7 +107,22 @@ result = requests.post(
     headers=headers
 )
 ```
-### Step 5: View the Service Invocation outputs
+
+### Step 5: Use with Multi-App Run
+
+You can run the Dapr applications in this quickstart with the [Multi-App Run template]({{< ref multi-app-dapr-run >}}). Instead of running two separate `dapr run` commands for the `order-processor` and `checkout` applications, run the following command:
+
+```sh
+dapr run -f .
+```
+
+To stop all applications, run:
+
+```sh
+dapr stop -f .
+```
+
+### Step 6: View the Service Invocation outputs
 
 Dapr invokes an application on any Dapr instance. In the code, the sidecar programming model encourages each application to talk to its own instance of Dapr. The Dapr instances then discover and communicate with one another.
 
@@ -225,7 +240,21 @@ const res = await axios.post(`${DAPR_HOST}:${DAPR_HTTP_PORT}/orders`, order , ax
 console.log("Order passed: " + res.config.data);
 ```
 
-### Step 5: View the Service Invocation outputs
+### Step 5: Use with Multi-App Run
+
+You can run the Dapr applications in this quickstart with the [Multi-App Run template]({{< ref multi-app-dapr-run >}}). Instead of running two separate `dapr run` commands for the `order-processor` and `checkout` applications, run the following command:
+
+```sh
+dapr run -f .
+```
+
+To stop all applications, run:
+
+```sh
+dapr stop -f .
+```
+
+### Step 6: View the Service Invocation outputs
 
 Dapr invokes an application on any Dapr instance. In the code, the sidecar programming model encourages each application to talk to its own instance of Dapr. The Dapr instances then discover and communicate with one another.
 
@@ -346,7 +375,21 @@ var response = await client.PostAsync($"{baseURL}/orders", content);
     Console.WriteLine("Order passed: " + order);
 ```
 
-### Step 5: View the Service Invocation outputs
+### Step 5: Use with Multi-App Run
+
+You can run the Dapr applications in this quickstart with the [Multi-App Run template]({{< ref multi-app-dapr-run >}}). Instead of running two separate `dapr run` commands for the `order-processor` and `checkout` applications, run the following command:
+
+```sh
+dapr run -f .
+```
+
+To stop all applications, run:
+
+```sh
+dapr stop -f .
+```
+
+### Step 6: View the Service Invocation outputs
 
 Dapr invokes an application on any Dapr instance. In the code, the sidecar programming model encourages each application to talk to its own instance of Dapr. The Dapr instances then discover and communicate with one another.
 
@@ -465,7 +508,21 @@ HttpResponse<String> response = httpClient.send(request, HttpResponse.BodyHandle
 System.out.println("Order passed: "+ orderId)
 ```
 
-### Step 5: View the Service Invocation outputs
+### Step 5: Use with Multi-App Run
+
+You can run the Dapr applications in this quickstart with the [Multi-App Run template]({{< ref multi-app-dapr-run >}}). Instead of running two separate `dapr run` commands for the `order-processor` and `checkout` applications, run the following command:
+
+```sh
+dapr run -f .
+```
+
+To stop all applications, run:
+
+```sh
+dapr stop -f .
+```
+
+### Step 6: View the Service Invocation outputs
 
 Dapr invokes an application on any Dapr instance. In the code, the sidecar programming model encourages each application to talk to its own instance of Dapr. The Dapr instances then discover and communicate with one another.
 
@@ -586,7 +643,21 @@ req.Header.Add("dapr-app-id", "order-processor")
 response, err := client.Do(req)
 ```
 
-### Step 5: View the Service Invocation outputs
+### Step 5: Use with Multi-App Run
+
+You can run the Dapr applications in this quickstart with the [Multi-App Run template]({{< ref multi-app-dapr-run >}}). Instead of running two separate `dapr run` commands for the `order-processor` and `checkout` applications, run the following command:
+
+```sh
+dapr run -f .
+```
+
+To stop all applications, run:
+
+```sh
+dapr stop -f .
+```
+
+### Step 6: View the Service Invocation outputs
 
 Dapr invokes an application on any Dapr instance. In the code, the sidecar programming model encourages each application to talk to its own instance of Dapr. The Dapr instances then discover and communicate with one another.
 
@@ -620,6 +691,7 @@ Dapr invokes an application on any Dapr instance. In the code, the sidecar progr
 == APP == Order received :  {"orderId":10}
 ```
 
+
 {{% /codetab %}}
 
 {{% /tabs %}}