Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs for components-path changed to resources-path #2999

Closed
wants to merge 3 commits into from
Closed

docs for components-path changed to resources-path #2999

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
7bfbf25
docs for components-path changed to resources-path
pravinpushkar Dec 8, 2022
417048f
doc for creation of resources direcotory instead of components
pravinpushkar Dec 14, 2022
34f2225
Merge branch 'v1.10' into resources-path
hhunter-ms Jan 18, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion daprdocs/content/en/getting-started/get-started-api.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ Launch a Dapr sidecar that will listen on port 3500 for a blank application name
dapr run --app-id myapp --dapr-http-port 3500
```

Since no custom component folder was defined with the above command, Dapr uses the default component definitions created during the [`dapr init` flow]({{< ref "install-dapr-selfhost.md#step-5-verify-components-directory-has-been-initialized" >}}).
Since no custom resources folder was defined with the above command, Dapr uses the default resources definitions created during the [`dapr init` flow]({{< ref "install-dapr-selfhost.md#step-5-verify-resources-directory-has-been-initialized" >}}).

### Step 2: Save state

Expand Down
10 changes: 5 additions & 5 deletions daprdocs/content/en/getting-started/install-dapr-selfhost.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ Dapr initialization includes:

1. Running a **Redis container instance** to be used as a local state store and message broker.
1. Running a **Zipkin container instance** for observability.
1. Creating a **default components folder** with component definitions for the above.
1. Creating a **default resources folder** with resources definitions for the above.
1. Running a **Dapr placement service container instance** for local actor support.

{{% alert title="Docker" color="primary" %}}
Expand Down Expand Up @@ -83,14 +83,14 @@ docker ps

<img src="/images/install-dapr-selfhost/docker-containers.png" width=800>

### Step 5: Verify components directory has been initialized
### Step 5: Verify resources directory has been initialized

On `dapr init`, the CLI also creates a default components folder that contains several YAML files with definitions for a state store, Pub/sub, and Zipkin. The Dapr sidecar will read these components and use:
On `dapr init`, the CLI also creates a default resources folder that contains several YAML files with definitions for a state store, Pub/sub, and Zipkin. The Dapr sidecar will read these resources and use:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
On `dapr init`, the CLI also creates a default resources folder that contains several YAML files with definitions for a state store, Pub/sub, and Zipkin. The Dapr sidecar will read these resources and use:
On `dapr init`, the CLI also creates a default resources folder that contains several YAML component files with specifications for a state store, pub/sub, and Zipkin. The Dapr sidecar loads these component resources and uses:


- The Redis container for state management and messaging.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- The Redis container for state management and messaging.
- The Redis container for both state management and pub/sub messaging.

- The Zipkin container for collecting traces.

Verify by opening your components directory:
Verify by opening your resources directory:

- On Windows, under `%UserProfile%\.dapr`
- On Linux/MacOS, under `~/.dapr`
Expand All @@ -105,7 +105,7 @@ ls $HOME/.dapr

**Output:**

`bin components config.yaml`
`bin resources config.yaml`

<br>

Expand Down
Loading