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

Cosmetic changes to getting started init

This commit is contained in:
Ori Zohar 2020-12-22 14:47:43 -08:00
parent a56e596d73
commit 0e84f649bc
3 changed files with 37 additions and 25 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
daprdocs/content/en/developing-applications/building-blocks/state-management/howto-get-save-state.md
View File

@ -22,7 +22,7 @@ For the purpose of this how to we'll use a Redis state store, but any state stor
{{< tabs "Self-Hosted (CLI)" Kubernetes>}}
{{% codetab %}}
When using `Dapr init` in Standalone mode, the Dapr CLI automatically provisions a state store (Redis) and creates the relevant YAML in a `components` directory, which for Linux/MacOS is `$HOME/.dapr/components` and for Windows is `%USERPROFILE%\.dapr\components`
When using `dapr init` in Standalone mode, the Dapr CLI automatically provisions a state store (Redis) and creates the relevant YAML in a `components` directory, which for Linux/MacOS is `$HOME/.dapr/components` and for Windows is `%USERPROFILE%\.dapr\components`
To change the state store being used, replace the YAML under `/components` with the file of your choice.
{{% /codetab %}}

18
daprdocs/content/en/getting-started/install-dapr-kubernetes.md
View File

@ -51,11 +51,13 @@ The `-k` flag initializes Dapr on the Kubernetes cluster in your current context
Make sure the correct "target" cluster is set. Check `kubectl context (kubectl config kubectl config get-contexts)` to verify. You can set a different context using `kubectl config use-context <CONTEXT>`.
{{% /alert %}}
Run `dapr init -k` on your local machine:
Run on your local machine:
```bash
$ dapr init -k
dapr init -k
```
```
⌛ Making the jump to hyperspace...
ℹ️ Note: To install Dapr using Helm, see here: https://github.com/dapr/docs/blob/master/getting-started/environment-setup.md#using-helm-advanced
@ -67,7 +69,7 @@ $ dapr init -k
The default namespace when initializing Dapr is `dapr-system`. You can override this with the `-n` flag.
```
```bash
dapr init -k -n mynamespace
```
@ -76,7 +78,7 @@ dapr init -k -n mynamespace
You can run Dapr with 3 replicas of each control plane pod with the exception of the Placement pod in the dapr-system namespace for [production scenarios]({{< ref kubernetes-production.md >}}).
```
```bash
dapr init -k --enable-ha=true
```
@ -84,14 +86,14 @@ dapr init -k --enable-ha=true
Dapr is initialized by default with [mTLS]({{< ref "security-concept.md#sidecar-to-sidecar-communication" >}}). You can disable it with:
```
```bash
dapr init -k --enable-mtls=false
```
### Uninstall Dapr on Kubernetes with CLI
```bash
$ dapr uninstall --kubernetes
dapr uninstall --kubernetes
```
## Install with Helm (advanced)
@ -130,8 +132,10 @@ The latest Dapr helm chart no longer supports Helm v2. Please migrate from helm
Once the chart installation is complete verify the dapr-operator, dapr-placement, dapr-sidecar-injector and dapr-sentry pods are running in the `dapr-system` namespace:
```bash
$ kubectl get pods -n dapr-system -w
kubectl get pods -n dapr-system -w
```
```
NAME READY STATUS RESTARTS AGE
dapr-dashboard-7bd6cbf5bf-xglsr 1/1 Running 0 40s
dapr-operator-7bd6cbf5bf-xglsr 1/1 Running 0 40s

42
daprdocs/content/en/getting-started/install-dapr-selfhost.md
View File

@ -1,9 +1,9 @@
---
type: docs
title: "How-To: Install Dapr into your local environment"
title: "How-To: Initialize Dapr in your local environment"
linkTitle: "Init Dapr locally"
weight: 20
description: "Install Dapr in your local environment for testing and self-hosting"
description: "Initialize Dapr in your local environment for testing and self-hosting"
aliases:
- /getting-started/install-dapr/
---
@ -40,31 +40,35 @@ This command downloads and installs Dapr runtime v0.11. To install v1.0-rc2 prev
{{< /tabs >}}
1. Run `dapr init`:
1. Run the `init` CLI command:
You can install or upgrade to a specific version of the Dapr runtime using `dapr init --runtime-version`. You can find the list of versions in [Dapr Release](https://github.com/dapr/dapr/releases)
```bash
$ dapr init
⌛ Making the jump to hyperspace...
Downloading binaries and setting up components
✅ Success! Dapr is up and running. To get started, go here: https://aka.ms/dapr-getting-started
```
dapr init
```
1. Verify Dapr version with `dapr --version`:
1. Verify Dapr version:
```bash
$ dapr --version
dapr --version
```
Output should look like this:
```
CLI version: 0.11
Runtime version: 0.11
```
1. Verify Dapr containers are running with `docker ps`:
1. Verify Dapr containers are running:
```bash
docker ps
```
Make sure the `daprio/dapr`, `openzipkin/zipkin`, and `redis` container images are all running:
```bash
$ docker ps
```
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
0dda6684dc2e openzipkin/zipkin "/busybox/sh run.sh" 2 minutes ago Up 2 minutes 9410/tcp, 0.0.0.0:9411->9411/tcp dapr_zipkin
9bf6ef339f50 redis "docker-entrypoint.s…" 2 minutes ago Up 2 minutes 0.0.0.0:6379->6379/tcp dapr_redis
@ -76,9 +80,13 @@ This command downloads and installs Dapr runtime v0.11. To install v1.0-rc2 prev
{{< tabs "Linux/MacOS" "Windows">}}
{{% codetab %}}
Run `ls $HOME/.dapr`:
Run:
```bash
$ ls $HOME/.dapr
ls $HOME/.dapr
```
Output should look like so:
```
bin components config.yaml
```
{{% /codetab %}}
@ -96,14 +104,14 @@ This command downloads and installs Dapr runtime v0.11. To install v1.0-rc2 prev
This cli command removes the placement Dapr container:
```bash
$ dapr uninstall
dapr uninstall
```
{{% alert title="Warning" color="warning" %}}
This command won't remove the Redis or Zipkin containers by default, just in case you were using them for other purposes. To remove Redis, Zipkin, Actor Placement container, as well as the default Dapr directory located at `$HOME/.dapr` or `%USERPROFILE%\.dapr\`, run:
```bash
$ dapr uninstall --all
dapr uninstall --all
```
{{% /alert %}}