mirror of https://github.com/dapr/docs.git
commit
b733ec95ae
|
@ -52,25 +52,25 @@ id = "UA-149338238-3"
|
|||
|
||||
# Top Nav Bar
|
||||
[[menu.main]]
|
||||
name = "Home"
|
||||
name = "Homepage"
|
||||
weight = 40
|
||||
url = "https://dapr.io"
|
||||
[[menu.main]]
|
||||
name = "About"
|
||||
name = "GitHub"
|
||||
weight = 50
|
||||
url = "https://dapr.io/#about"
|
||||
[[menu.main]]
|
||||
name = "Download"
|
||||
weight = 60
|
||||
url = "https://dapr.io/#download"
|
||||
url = "https://github.com/dapr"
|
||||
[[menu.main]]
|
||||
name = "Blog"
|
||||
weight = 70
|
||||
weight = 60
|
||||
url = "https://blog.dapr.io/posts"
|
||||
[[menu.main]]
|
||||
name = "Discord"
|
||||
weight = 70
|
||||
url = "https://aka.ms/dapr-discord"
|
||||
[[menu.main]]
|
||||
name = "Community"
|
||||
weight = 80
|
||||
url = "https://dapr.io/#community"
|
||||
url = "https://github.com/dapr/community/blob/master/README.md"
|
||||
|
||||
[params]
|
||||
copyright = "Dapr"
|
||||
|
|
|
@ -6,4 +6,4 @@ weight: 60
|
|||
description: See and measure the message calls across components and networked services
|
||||
---
|
||||
|
||||
This section includes guides for developers in the context of observability. See other sections for a [general overview of the observability concept]({{< ref observability >}}) in Dapr and for [operations guidance on monitoring]({{< ref monitoring >}}).
|
||||
This section includes guides for developers in the context of observability. See other sections for a [general overview of the observability concept]({{< ref observability-concept >}}) in Dapr and for [operations guidance on monitoring]({{< ref monitoring >}}).
|
||||
|
|
|
@ -108,7 +108,7 @@ The diagram below shows sequence 1-7 again on a local machine showing the API ca
|
|||
4. The Node.js app's sidecar forwards the request to the Node.js app. The Node.js app performs its business logic, logging the incoming message and then persist the order ID into Redis (not shown in the diagram)
|
||||
5. The Node.js app sends a response to the Python app through the Node.js sidecar.
|
||||
6. Dapr forwards the response to the Python Dapr sidecar
|
||||
7. The Python app receives the resposne.
|
||||
7. The Python app receives the response.
|
||||
|
||||
## Next steps
|
||||
|
||||
|
|
|
@ -23,9 +23,44 @@ Let's get started!
|
|||
|
||||
## Add Dapr as an 'External Tool'
|
||||
|
||||
First, quit IntelliJ.
|
||||
First, quit IntelliJ before modifying the configurations file directly.
|
||||
|
||||
Create or edit the file in `$HOME/.IdeaIC2019.3/config/tools/External\ Tools.xml` (change IntelliJ version in path if needed) to add a new `<tool></tool>` entry:
|
||||
### IntelliJ configuration file location
|
||||
For versions [2020.1](https://www.jetbrains.com/help/idea/2020.1/tuning-the-ide.html#config-directory) and above the configuration files for tools should be located in:
|
||||
|
||||
{{< tabs Windows Linux MacOS >}}
|
||||
|
||||
{{% codetab %}}
|
||||
|
||||
```powershell
|
||||
%USERPROFILE%\AppData\Roaming\JetBrains\IntelliJIdea2020.1\tools\
|
||||
```
|
||||
{{% /codetab %}}
|
||||
|
||||
|
||||
{{% codetab %}}
|
||||
```shell
|
||||
$HOME/.config/JetBrains/IntelliJIdea2020.1/tools/
|
||||
```
|
||||
{{% /codetab %}}
|
||||
|
||||
|
||||
{{% codetab %}}
|
||||
```shell
|
||||
~/Library/Application Support/JetBrains/IntelliJIdea2020.1/tools/
|
||||
```
|
||||
{{% /codetab %}}
|
||||
|
||||
|
||||
{{< /tabs >}}
|
||||
|
||||
> The configuration file location is different for version 2019.3 or prior. See [here](https://www.jetbrains.com/help/idea/2019.3/tuning-the-ide.html#config-directory) for more details.
|
||||
|
||||
Change the version of IntelliJ in the path if needed.
|
||||
|
||||
Create or edit the file in `<CONFIG PATH>/tools/External\ Tools.xml` (change IntelliJ version in path if needed). The `<CONFIG PATH>` is OS dependennt as seen above.
|
||||
|
||||
Add a new `<tool></tool>` entry:
|
||||
|
||||
```xml
|
||||
<toolSet name="External Tools">
|
||||
|
@ -33,10 +68,10 @@ Create or edit the file in `$HOME/.IdeaIC2019.3/config/tools/External\ Tools.xml
|
|||
<!-- 1. Each tool has its own app-id, so create one per application to be debugged -->
|
||||
<tool name="dapr for DemoService in examples" description="Dapr sidecar" showInMainMenu="false" showInEditor="false" showInProject="false" showInSearchPopup="false" disabled="false" useConsole="true" showConsoleOnStdOut="true" showConsoleOnStdErr="true" synchronizeAfterRun="true">
|
||||
<exec>
|
||||
<!-- 2. For Linux or MacOS use: /usr/local/bin/daprd -->
|
||||
<option name="COMMAND" value="C:\dapr\daprd.exe" />
|
||||
<!-- 2. For Linux or MacOS use: /usr/local/bin/dapr -->
|
||||
<option name="COMMAND" value="C:\dapr\dapr.exe" />
|
||||
<!-- 3. Choose app, http and grpc ports that do not conflict with other daprd command entries (placement address should not change). -->
|
||||
<option name="PARAMETERS" value="-app-id demoservice -app-port 3000 -dapr-http-port 3005 -dapr-grpc-port 52000 -placement-host-address localhost:50005" />
|
||||
<option name="PARAMETERS" value="run -app-id demoservice -app-port 3000 -dapr-http-port 3005 -dapr-grpc-port 52000 />
|
||||
<!-- 4. Use the folder where the `components` folder is located -->
|
||||
<option name="WORKING_DIRECTORY" value="C:/Code/dapr/java-sdk/examples" />
|
||||
</exec>
|
||||
|
@ -53,7 +88,7 @@ Optionally, you may also create a new entry for a sidecar tool that can be reuse
|
|||
<!-- 1. Reusable entry for apps with app port. -->
|
||||
<tool name="dapr with app-port" description="Dapr sidecar" showInMainMenu="false" showInEditor="false" showInProject="false" showInSearchPopup="false" disabled="false" useConsole="true" showConsoleOnStdOut="true" showConsoleOnStdErr="true" synchronizeAfterRun="true">
|
||||
<exec>
|
||||
<!-- 2. For Linux or MacOS use: /usr/bin/dapr -->
|
||||
<!-- 2. For Linux or MacOS use: /usr/local/bin/dapr -->
|
||||
<option name="COMMAND" value="c:\dapr\dapr.exe" />
|
||||
<!-- 3. Prompts user 4 times (in order): app id, app port, Dapr's http port, Dapr's grpc port. -->
|
||||
<option name="PARAMETERS" value="run --app-id $Prompt$ --app-port $Prompt$ --dapr-http-port $Prompt$ --dapr-grpc-port $Prompt$" />
|
||||
|
@ -64,7 +99,7 @@ Optionally, you may also create a new entry for a sidecar tool that can be reuse
|
|||
<!-- 1. Reusable entry for apps without app port. -->
|
||||
<tool name="dapr without app-port" description="Dapr sidecar" showInMainMenu="false" showInEditor="false" showInProject="false" showInSearchPopup="false" disabled="false" useConsole="true" showConsoleOnStdOut="true" showConsoleOnStdErr="true" synchronizeAfterRun="true">
|
||||
<exec>
|
||||
<!-- 2. For Linux or MacOS use: /usr/bin/dapr -->
|
||||
<!-- 2. For Linux or MacOS use: /usr/local/bin/dapr -->
|
||||
<option name="COMMAND" value="c:\dapr\dapr.exe" />
|
||||
<!-- 3. Prompts user 3 times (in order): app id, Dapr's http port, Dapr's grpc port. -->
|
||||
<option name="PARAMETERS" value="run --app-id $Prompt$ --dapr-http-port $Prompt$ --dapr-grpc-port $Prompt$" />
|
||||
|
@ -108,3 +143,7 @@ After debugging, make sure you stop both `dapr` and your app in IntelliJ.
|
|||
>Note: Since you launched the service(s) using the **dapr** ***run*** CLI command, the **dapr** ***list*** command will show runs from IntelliJ in the list of apps that are currently running with Dapr.
|
||||
|
||||
Happy debugging!
|
||||
|
||||
## Related links
|
||||
|
||||
- [Change](https://intellij-support.jetbrains.com/hc/en-us/articles/206544519-Directories-used-by-the-IDE-to-store-settings-caches-plugins-and-logs) in IntelliJ configuration directory location
|
||||
|
|
Loading…
Reference in New Issue