dapr
/
docs
mirror of https://github.com/dapr/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'v1.0' into dotnet-sdkdocs

This commit is contained in:
Aaron Crawfis 2021-03-01 12:10:49 -08:00 committed by GitHub
parent 4cff5ca0fb 1efbe43e65
commit c2ab817bf6
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
4 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
daprdocs/content/en/concepts/security-concept.md
View File

@ -50,7 +50,7 @@ The diagram below shows how the Sentry system service issues certificates for ap
<img src="/images/security-mTLS-sentry-selfhosted.png" width=1000>
### mTLS in Kubernetes
The diagram below shows how the Sentry system service issues certificates for applications based on the root/issuer certificate that is provided by an operator or generated by the Sentry service as stored as a Kubernetes secret
The diagram below shows how the Sentry system service issues certificates for applications based on the root/issuer certificate that is provided by an operator or generated by the Sentry service and stored as a Kubernetes secret
<img src="/images/security-mTLS-sentry-kubernetes.png" width=1000>

2
daprdocs/content/en/getting-started/get-started-api.md
View File

@ -19,7 +19,7 @@ Run the following command to launch a Dapr sidecar that will listen on port 3500
dapr run --app-id myapp --dapr-http-port 3500
```
With this command, no custom component folder was defined so the Dapr uses the default component definitions that were created during the init flow (these can be found under `$HOME/.dapr/components` on Linux or MacOS and under `%USERPROFILE%\.dapr\components` on Windows). These tell Dapr to the local Redis Docker container as a state store and message broker.
With this command, no custom component folder was defined, so Dapr uses the default component definitions that were created during the init flow (these can be found under `$HOME/.dapr/components` on Linux or MacOS and under `%USERPROFILE%\.dapr\components` on Windows). These tell Dapr to use the local Redis Docker container as a state store and message broker.
## Step 2: Save state

2
daprdocs/content/en/operations/components/setup-pubsub/supported-pubsub/setup-nats-streaming.md
View File

@ -78,7 +78,7 @@ The above example uses secrets as plain strings. It is recommended to use a secr
You can run a NATS server locally using Docker:
```bash
docker run -d -name nats-streaming -p 4222:4222 -p 8222:8222 nats-streaming
docker run -d --name nats-streaming -p 4222:4222 -p 8222:8222 nats-streaming
```
You can then interact with the server using the client port: `localhost:4222`.

4
daprdocs/content/en/operations/components/setup-state-store/supported-state-stores/setup-mysql.md
View File

@ -64,7 +64,7 @@ Run an instance of MySQL. You can run a local instance of MySQL in Docker CE wit
This example does not describe a production configuration because it sets the password in plain text and the user name is left as the MySQL default of "root".
```bash
docker run --name dapr_mysql -p 3306:3306 -e MYSQL_ROOT_PASSWORD=my-secret-pw -d mysql:latest
docker run --name dapr-mysql -p 3306:3306 -e MYSQL_ROOT_PASSWORD=my-secret-pw -d mysql:latest
```
{{% /codetab %}}
@ -78,7 +78,7 @@ We can use [Helm](https://helm.sh/) to quickly create a MySQL instance in our Ku
```bash
helm repo add bitnami https://charts.bitnami.com/bitnami
helm install dapr_mysql bitnami/mysql
helm install dapr-mysql bitnami/mysql
```
1. Run `kubectl get pods` to see the MySQL containers now running in your cluster.