PostgreSQL updates

This commit is contained in:
Brooke Hamilton 2020-07-08 19:00:49 -04:00
parent a43d06df30
commit 5dd0d62738
1 changed files with 3 additions and 4 deletions

View File

@ -5,8 +5,7 @@ This article provides guidance on configuring a PostgreSQL state store.
## Create a PostgreSQL Store
Dapr can use any PostgreSQL instance. If you already have a running instance of PostgreSQL, move on to the [Create a Dapr component](#create-a-dapr-component) section.
1. Run an instance of PostgreSQL
You can run a local instance of PostgreSQL in Docker CE with the following command:
1. Run an instance of PostgreSQL. You can run a local instance of PostgreSQL in Docker CE with the following command:
This example does not describe a production configuration because it sets the password in plain text and the user name is left as the PostgreSQL default of "postgres".
@ -25,7 +24,7 @@ Either the default "postgres" database can be used, or create a new database for
## Create a Dapr component
Create a file called `postgres.yaml`, and paste the following. If you want to also configure PostgreSQL to store actors, add the `actorStateStore` configuration element shown below.
Create a file called `postgres.yaml`, and paste the following and replace the `<CONNECTION STRING>` value with your connection string. If you want to also configure PostgreSQL to store actors, add the `actorStateStore` configuration element shown below.
```yaml
apiVersion: dapr.io/v1alpha1
@ -40,7 +39,7 @@ spec:
- name: actorStateStore
value: "true"
```
The above example uses secrets as plain strings. It is recommended to use a secret store for the secrets as described [here](../../concepts/secrets/README.md)
The above example uses secrets as plain strings. It is recommended to use a secret store for the secrets as described [here](../../concepts/secrets/README.md).
## Apply the configuration