diff --git a/daprdocs/content/en/developing-applications/local-development/multi-app-dapr-run/multi-app-template.md b/daprdocs/content/en/developing-applications/local-development/multi-app-dapr-run/multi-app-template.md index 6dad64c9f..8bca30080 100644 --- a/daprdocs/content/en/developing-applications/local-development/multi-app-dapr-run/multi-app-template.md +++ b/daprdocs/content/en/developing-applications/local-development/multi-app-dapr-run/multi-app-template.md @@ -83,7 +83,7 @@ apps: appProtocol: http appPort: 8080 appHealthCheckPath: "/healthz" - command: ["python3" "app.py"] + command: ["python3", "app.py"] appLogDestination: file # (optional), can be file, console or fileAndConsole. default is fileAndConsole. daprdLogDestination: file # (optional), can be file, console or fileAndConsole. default is file. - appID: backend # optional diff --git a/daprdocs/content/en/reference/components-reference/supported-pubsub/setup-inmemory.md b/daprdocs/content/en/reference/components-reference/supported-pubsub/setup-inmemory.md index 8a6a8951b..e2275a465 100644 --- a/daprdocs/content/en/reference/components-reference/supported-pubsub/setup-inmemory.md +++ b/daprdocs/content/en/reference/components-reference/supported-pubsub/setup-inmemory.md @@ -1,13 +1,13 @@ --- type: docs -title: "In Memory" -linkTitle: "In Memory" +title: "In-memory" +linkTitle: "In-memory" description: "Detailed documentation on the In Memory pubsub component" aliases: - "/operations/components/setup-pubsub/supported-pubsub/setup-inmemory/" --- -The In Memory pub/sub component is useful for development purposes and works inside of a single machine boundary. +The in-memory pub/sub component operates within a single Dapr sidecar. This is primarily meant for development purposes. State is not replicated across multiple sidecars and is lost when the Dapr sidecar is restarted. ## Component format @@ -25,6 +25,7 @@ spec: > Note: in-memory does not require any specific metadata for the component to work, however spec.metadata is a required field. ## Related links + - [Basic schema for a Dapr component]({{< ref component-schema >}}) in the Related links section - Read [this guide]({{< ref "howto-publish-subscribe.md#step-2-publish-a-topic" >}}) for instructions on configuring pub/sub components - [Pub/Sub building block]({{< ref pubsub >}}) diff --git a/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-inmemory.md b/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-inmemory.md index d54277d17..17d8cc4be 100644 --- a/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-inmemory.md +++ b/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-inmemory.md @@ -1,20 +1,16 @@ --- type: docs -title: "In Memory" -linkTitle: "In Memory" -description: "Detailed documentation on the In Memory state component" +title: "In-memory" +linkTitle: "In-memory" +description: "Detailed documentation on the in-memory state component" aliases: - "/operations/components/setup-state-store/supported-state-stores/setup-inmemory/" --- -The In Memory state store component is useful for development purposes and works inside of a single machine boundary. - -{{% alert title="Warning" color="warning" %}} - This component **shouldn't be used for production**. It is developer only and will never be stable. If you come across a scenario and want to use it in production, you can submit an issue and discuss it with the community. - -{{% /alert %}} +The in-memory state store component maintains state in the Dapr sidecar's memory. This is primarily meant for development purposes. State is not replicated across multiple sidecars and is lost when the Dapr sidecar is restarted. ## Component format + To setup in-memory state store, create a component of type `state.in-memory`. See [this guide]({{< ref "howto-get-save-state.md#step-1-setup-a-state-store" >}}) on how to create and apply a state store configuration. ```yaml @@ -31,6 +27,7 @@ spec: > Note: While in-memory does not require any specific metadata for the component to work, `spec.metadata` is a required field. ## Related links + - [Basic schema for a Dapr component]({{< ref component-schema >}}) - Learn [how to create and configure state store components]({{< ref howto-get-save-state.md >}}) - Read more about the [state management building block]({{< ref state-management >}}) diff --git a/daprdocs/data/components/pubsub/generic.yaml b/daprdocs/data/components/pubsub/generic.yaml index 4ceabbfa6..38d775c63 100644 --- a/daprdocs/data/components/pubsub/generic.yaml +++ b/daprdocs/data/components/pubsub/generic.yaml @@ -1,6 +1,6 @@ - component: In-memory link: setup-inmemory - state: Beta + state: Stable version: v1 since: "1.7" features: diff --git a/daprdocs/data/components/state_stores/generic.yaml b/daprdocs/data/components/state_stores/generic.yaml index dd7cacd13..a4ffcd52c 100644 --- a/daprdocs/data/components/state_stores/generic.yaml +++ b/daprdocs/data/components/state_stores/generic.yaml @@ -77,9 +77,9 @@ query: false - component: In-memory link: setup-inmemory - state: Developer-only + state: Stable version: v1 - since: "1.8" + since: "1.9" features: crud: true transactions: true diff --git a/daprdocs/layouts/partials/page-meta-links.html b/daprdocs/layouts/partials/page-meta-links.html index 6bf0d95a1..7e87f5bd2 100644 --- a/daprdocs/layouts/partials/page-meta-links.html +++ b/daprdocs/layouts/partials/page-meta-links.html @@ -1,28 +1,53 @@ -{{ if .Path }} -{{ $pathFormatted := replace .Path "\\" "/" }} -{{ $gh_repo := ($.Param "github_repo") }} -{{ $gh_subdir := ($.Param "github_subdir") }} -{{ $gh_project_repo := ($.Param "github_project_repo") }} -{{ $gh_branch := (default "master" ($.Param "github_branch")) }} -{{ if $gh_repo }} -