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

Fixing some indentation

This commit is contained in:
lolorol 2020-02-10 14:28:56 +08:00
parent 2dacb2f430
commit 2beb3888b0
3 changed files with 39 additions and 24 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
README.md
View File

@ -23,12 +23,12 @@ Dapr is currently under community development in preview phase and master branch
## SDKs
- **[Go SDK](https://github.com/dapr/go-sdk)** - Get started with the Dapr proto client for Go
- **[Java SDK](https://github.com/dapr/java-sdk)** - Get started with the Dapr proto client for Java
- **[Javascript SDK](https://github.com/dapr/js-sdk)** - Get started with the Dapr proto client for Javascript
- **[Python SDK](https://github.com/dapr/python-sdk)** - Get started with the Dapr proto client for Python
- **[.NET SDK](https://github.com/dapr/dotnet-sdk)** - Get started with the Dapr proto client for .NET Core
- **[Getting Started with .NET Actors](https://github.com/dapr/dotnet-sdk/blob/master/docs/get-started-dapr-actor.md)** - Tutorial for developing actor applications using the Dapr .NET SDK including **[actor samples](https://github.com/dapr/dotnet-sdk/tree/master/samples/Actor)**
- **[Getting Started with ASP.NET Core](https://github.com/dapr/dotnet-sdk/tree/master/samples/AspNetCore)** - Samples for developing ASP.NET applications using the Dapr .NET SDK
- **[Go SDK](https://github.com/dapr/go-sdk)** - Get started with the Dapr proto client for Go
- **[Java SDK](https://github.com/dapr/java-sdk)** - Get started with the Dapr proto client for Java
- **[Javascript SDK](https://github.com/dapr/js-sdk)** - Get started with the Dapr proto client for Javascript
- **[Python SDK](https://github.com/dapr/python-sdk)** - Get started with the Dapr proto client for Python
- **[.NET SDK](https://github.com/dapr/dotnet-sdk)** - Get started with the Dapr proto client for .NET Core
- **[Getting Started with .NET Actors](https://github.com/dapr/dotnet-sdk/blob/master/docs/get-started-dapr-actor.md)** - Tutorial for developing actor applications using the Dapr .NET SDK including **[actor samples](https://github.com/dapr/dotnet-sdk/tree/master/samples/Actor)**
- **[Getting Started with ASP.NET Core](https://github.com/dapr/dotnet-sdk/tree/master/samples/AspNetCore)** - Samples for developing ASP.NET applications using the Dapr .NET SDK
> Note: Dapr is language agnostic and provides a [RESTful HTTP API](./reference/api/README.md) in addition to the protobuf clients.

34
best-practices/troubleshooting/common_issues.md
View File

@ -44,7 +44,7 @@ If this is the case, restarting the pods will fix the issue.
In order to further diagnose any issue, check the logs of the Dapr sidecar injector:
```
```bash
kubectl logs -l app=dapr-sidecar-injector -n dapr-system
```
@ -56,7 +56,9 @@ Have you installed an Dapr State store in your cluster?
To check, use kubectl get a list of components:
`kubectl get components`
```bash
kubectl get components
```
If there isn't a state store component, it means you need to set one up.
Visit [here](../../howto/setup-state-store/setup-redis.md) for more details.
@ -64,7 +66,9 @@ Visit [here](../../howto/setup-state-store/setup-redis.md) for more details.
If everything's set up correctly, make sure you got the credentials right.
Search the Dapr runtime logs and look for any state store errors:
`kubectl logs <name-of-pod> daprd`.
```bash
kubectl logs <name-of-pod> daprd
```
### I am unable to publish and receive events
@ -72,20 +76,28 @@ Have you installed an Dapr Message Bus in your cluster?
To check, use kubectl get a list of components:
`kubectl get components`
```bash
kubectl get components
```
If there isn't a pub/sub component, it means you need to set one up.
Visit [here](../../howto/setup-pub-sub-message-broker/README.md) for more details.
If everything's set up correctly, make sure you got the credentials right.
If everything is set up correctly, make sure you got the credentials right.
Search the Dapr runtime logs and look for any pub/sub errors:
`kubectl logs <name-of-pod> daprd`.
```bash
kubectl logs <name-of-pod> daprd
```
### The Dapr Operator pod keeps crashing
Check that there's only one installation of the Dapr Operator in your cluster.
Find out by running `kubectl get pods -l app=dapr-operator --all-namespaces`.
Find out by running
```bash
kubectl get pods -l app=dapr-operator --all-namespaces
```
If two pods appear, delete the redundant Dapr installation.
@ -94,7 +106,9 @@ If two pods appear, delete the redundant Dapr installation.
This means there are some internal issue inside the Dapr runtime.
To diagnose, view the logs of the sidecar:
`kubectl logs <name-of-pod> daprd`.
```bash
kubectl logs <name-of-pod> daprd
```
### I'm getting 404 Not Found responses when calling Dapr
@ -122,6 +136,8 @@ If you still can't find the issue, try enabling `debug` log levels for the Dapr
You might also want to look at error logs from your own process. If running on Kubernetes, find the pod containing your app, and execute the following:
`kubectl logs <pod-name> <name-of-your-container>`.
```bash
kubectl logs <pod-name> <name-of-your-container>
```
If running in Standalone mode, you should see the stderr and stdout outputs from your app displayed in the main console session.

13
overview.md
View File

@ -31,14 +31,13 @@ Each of these building blocks is independent, meaning that you can use one, some
•**Actors** A pattern for stateful and stateless objects that make concurrency simple with method and state encapsulation. Dapr provides many capabilities in its actor runtime including concurrency, state, life-cycle management for actor activation/deactivation and timers and reminders to wake-up actors.
The diagram below shows the distributed system building blocks provides by Dapr, exposed with standard APIs. These APIs can be used from any developer code over http or gRPC. Dapr integrates with any hosting platform, for example Kubernetes, to enable application portability including across cloud and edge.
![Dapr overview](images/overview.png)
## Sidecar architecture
Dapr exposes its APIs as a sidecar architecture, either as a container or as a process, not requiring the application code to include any Dapr runtime code. This makes integration with Dapr easy from other runtimes, as well as providing separation of the application logic for improved supportability.
Dapr exposes its APIs as a sidecar architecture, either as a container or as a process, not requiring the application code to include any Dapr runtime code. This makes integration with Dapr easy from other runtimes, as well as providing separation of the application logic for improved supportability.
![Dapr overview](images/overview-sidecar.png)
@ -46,7 +45,7 @@ In container hosting environments such a Kubernetes, Dapr runs as a side-car con
![Dapr overview](images/overview-sidecar-kubernetes.png)
## Developer language SDKs and frameworks
## Developer language SDKs and frameworks
To make using Dapr more natural for different languages, it also includes language specific SDKs for Go, Java, JavaScript, .NET and Python. These SDKs expose the functionality in the Dapr building blocks, such as saving state, publishing an event or creating an actor, through a typed, language API rather than calling the http/gRPC API. This enables you to write a combination of stateless and stateful functions and actors all in the language of their choice. And because these SDKs share the Dapr runtime, you get cross-language actor and functions support.
@ -60,15 +59,15 @@ You can use the [Dapr CLI](https://github.com/dapr/cli) to run services locally.
![Dapr overview](images/overview_standalone.png)
For more information on the actor *Placement* service see [actor overview](/concepts/actor/actor_overview.md#distribution-and-failover)
For more information on the actor *Placement* service see [actor overview](/concepts/actor/actor_overview.md#distribution-and-failover)
## Running Dapr in Kubernetes mode
## Running Dapr in Kubernetes mode
Dapr can be configured to run on any [Kubernetes cluster](https://github.com/dapr/samples/tree/master/2.hello-kubernetes). In Kubernetes the *dapr-sidecar-injector* and *dapr-operator* services provide first class integration to launch Dapr as a sidecar container in the same pod as the service and provides notifications of Dapr component updates provisioned into the cluster.
![Dapr overview](images/overview_kubernetes.png)
For more information on the actor *Placement* service see [actor overview](/concepts/actor/actor_overview.md#distribution-and-failover)
For more information on the actor *Placement* service see [actor overview](/concepts/actor/actor_overview.md#distribution-and-failover)
In order to give your service an id and port known to Dapr and launch the Dapr sidecar container, you simply annotate your deployment like this.