mirror of https://github.com/dapr/samples.git
Update docs links to new platform (#31)
This commit is contained in:
parent
1696fcdc7e
commit
ceaf39439a
|
|
@ -46,7 +46,7 @@ Before you file an issue, make sure you've checked the following:
|
|||
- 👎 down-vote
|
||||
1. For bugs
|
||||
- Check it's not an environment issue. For example, if running on Kubernetes, make sure prerequisites are in place. (state stores, bindings, etc.)
|
||||
- You have as much data as possible. This usually comes in the form of logs and/or stacktrace. If running on Kubernetes or other environment, look at the logs of the Dapr services (runtime, operator, placement service). More details on how to get logs can be found [here](https://github.com/dapr/docs/tree/master/best-practices/troubleshooting/logs.md).
|
||||
- You have as much data as possible. This usually comes in the form of logs and/or stacktrace. If running on Kubernetes or other environment, look at the logs of the Dapr services (runtime, operator, placement service). More details on how to get logs can be found [here](https://docs.dapr.io/operations/troubleshooting/logs-troubleshooting/.
|
||||
1. For proposals
|
||||
- Many changes to the Dapr runtime may require changes to the API. In that case, the best place to discuss the potential feature is the main [Dapr repo](https://github.com/dapr/dapr).
|
||||
- Other examples could include bindings, state stores or entirely new components.
|
||||
|
|
|
|||
|
|
@ -6,8 +6,8 @@ Samples in this repository showcase [Dapr](https://dapr.io/) capabilities using
|
|||
|
||||
If you are new to Dapr, you may want to review following resources first:
|
||||
|
||||
* [Getting started with Dapr](https://github.com/dapr/docs/blob/master/getting-started/README.md)
|
||||
* [Dapr overview](https://github.com/dapr/docs/blob/master/overview/README.md)
|
||||
* [Getting started with Dapr](https://docs.dapr.io/getting-started/)
|
||||
* [Dapr overview](https://docs.dapr.io/concepts/overview/)
|
||||
* [Dapr quickstarts](https://github.com/dapr/quickstarts) - a collection of simple tutorials covering Dapr's main capabilities
|
||||
|
||||
> Note, these samples are maintained by the Dapr community and are not guaranteed to work properly with the latest Dapr runtime version.
|
||||
|
|
|
|||
|
|
@ -49,8 +49,8 @@ Run [this script](scripts/deploy_aks.ps1) to deploy an AKS cluster or follow the
|
|||
References:
|
||||
|
||||
* [Deploy AKS using Portal](https://docs.microsoft.com/en-us/azure/aks/kubernetes-walkthrough-portal)
|
||||
* [Deploy AKS using CLI](https://github.com/dapr/docs/blob/master/getting-started/cluster/setup-aks.md)
|
||||
* [Dapr Environment - Setup Cluster](https://github.com/dapr/docs/blob/master/getting-started/environment-setup.md#setup-cluster)
|
||||
* [Deploy AKS using CLI](https://docs.dapr.io/operations/hosting/kubernetes/cluster/setup-aks/)
|
||||
* [Dapr Environment - Setup Cluster](https://docs.dapr.io/getting-started/install-dapr/#setup-cluster)
|
||||
|
||||
## Install Dapr
|
||||
|
||||
|
|
@ -65,8 +65,8 @@ helm install dapr dapr/dapr --namespace dapr-system
|
|||
|
||||
References:
|
||||
|
||||
* [Dapr Environment Setup](https://github.com/dapr/docs/blob/master/getting-started/environment-setup.md)
|
||||
* [Install Dapr on a Kubernetes cluster using Helm](https://github.com/dapr/docs/blob/master/getting-started/environment-setup.md#using-helm-advanced)
|
||||
* [Dapr Environment Setup](https://docs.dapr.io/getting-started/install-dapr/)
|
||||
* [Install Dapr on a Kubernetes cluster using Helm](https://docs.dapr.io/getting-started/install-dapr/#install-with-helm-advanced)
|
||||
|
||||
## Create Blob Storage
|
||||
|
||||
|
|
@ -338,8 +338,8 @@ Run [this script](scripts/deploy_redis.ps1) to execute steps 1 through 2 or foll
|
|||
|
||||
References:
|
||||
|
||||
* [Setup Redis](https://github.com/RicardoNiepel/dapr-docs/blob/master/howto/setup-state-store/setup-redis.md)
|
||||
* [Setup other state stores](https://github.com/dapr/docs/tree/master/howto/setup-state-store)
|
||||
* [Setup Redis](https://docs.dapr.io/getting-started/configure-redis/)
|
||||
* [Setup other state stores](https://docs.dapr.io/operations/components/setup-state-store/supported-state-stores/)
|
||||
|
||||
## Service Bus
|
||||
|
||||
|
|
@ -382,7 +382,7 @@ Run [this script](scripts/deploy_servicebus.ps1) to execute steps 1 through 4 or
|
|||
References:
|
||||
|
||||
* [Create a Service Bus namespace and topic](https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-quickstart-topics-subscriptions-portal)
|
||||
* [Setup a Dapr pub/sub](https://github.com/dapr/docs/tree/master/howto/setup-pub-sub-message-broker)
|
||||
* [Setup a Dapr pub/sub](https://docs.dapr.io/developing-applications/building-blocks/pubsub/howto-publish-subscribe/)
|
||||
|
||||
## Set up distributed tracing
|
||||
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ In addition, we will overview the use of APIM tracing to debug your configuratio
|
|||
|
||||
* [Azure account](https://azure.microsoft.com/en-us/free/)
|
||||
* [Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)
|
||||
* [Kubernetes cluster with Dapr](https://github.com/dapr/docs/blob/v0.9.0/getting-started/environment-setup.md#installing-dapr-on-a-kubernetes-cluster)
|
||||
* [Kubernetes cluster with Dapr](https://docs.dapr.io/getting-started/install-dapr/#install-dapr-on-a-kubernetes-cluster)
|
||||
* [Helm](https://helm.sh/docs/intro/install/)
|
||||
|
||||
| Attribute | Details |
|
||||
|
|
@ -33,7 +33,7 @@ You will see a few different APIs being used throughout this demo. At one point
|
|||
|
||||
* [Azure API](https://docs.microsoft.com/en-us/rest/api/apimanagement/) - this is the API provided by Azure to manage its service (yes, including the API Management Service)
|
||||
* [API in APIM](https://docs.microsoft.com/en-us/azure/api-management/edit-api) - is the API which we will define in APIM service. Its operations will be used by the users
|
||||
* [Dapr API](https://github.com/dapr/docs/tree/master/reference/api#dapr-api-reference) - are the RESTful HTTP APIs defined by Dapr which developers interact with building applications
|
||||
* [Dapr API](https://docs.dapr.io/reference/api/) - are the RESTful HTTP APIs defined by Dapr which developers interact with building applications
|
||||
|
||||
## Setup
|
||||
|
||||
|
|
@ -321,7 +321,7 @@ Switching now to the Kubernetes cluster...
|
|||
|
||||
### Dependencies
|
||||
|
||||
To showcase the ability to expose Dapr pub/sub and binding APIs in APIM, we are going to need [Dapr components](https://github.com/dapr/docs/tree/master/concepts#components) configured on the cluster.
|
||||
To showcase the ability to expose Dapr pub/sub and binding APIs in APIM, we are going to need [Dapr components](https://docs.dapr.io/concepts/components-concept/) configured on the cluster.
|
||||
|
||||
> Note, while Dapr supports some 75+ different components, to keep things simple in this demo we will use Redis as both pub/sub and binding backing service
|
||||
|
||||
|
|
@ -344,7 +344,7 @@ kubectl rollout status statefulset.apps/redis-slave
|
|||
|
||||
### Dapr Components
|
||||
|
||||
Dapr's modular design means that we can easily extend its functionality using [components](https://github.com/dapr/docs/tree/master/concepts#components). The specific implementation for these components which can be any number of the readily available Dapr building blocks is done in configuration. That means that it's also easy to swap or reconfigure them at runtime without the need to modify your code.
|
||||
Dapr's modular design means that we can easily extend its functionality using [components](https://docs.dapr.io/concepts/components-concept/). The specific implementation for these components which can be any number of the readily available Dapr building blocks is done in configuration. That means that it's also easy to swap or reconfigure them at runtime without the need to modify your code.
|
||||
|
||||

|
||||
|
||||
|
|
@ -388,7 +388,7 @@ annotations:
|
|||
dapr.io/port: "8080"
|
||||
```
|
||||
|
||||
> To learn more about Kubernetes sidecar configuration see [Dapr docs](https://github.com/dapr/docs/blob/master/concepts/configuration/README.md#kubernetes-sidecar-configuration).
|
||||
> To learn more about Kubernetes sidecar configuration see [Dapr docs](https://docs.dapr.io/operations/configuration/configuration-overview/#kubernetes-sidecar).
|
||||
|
||||
For this demo we will use pre-build Docker images of two applications: [gRPC Echo Service](src/grpc-echo-service) and [HTTP Event Subscriber](src/http-event-subscriber). The Kubernetes deployment files for both of these are located here:
|
||||
|
||||
|
|
|
|||
|
|
@ -21,7 +21,7 @@ This sample requires you to have the following installed on your machine:
|
|||
|
||||
## Step 1 - Setup Dapr (Slim Init)
|
||||
|
||||
Follow [instructions](https://github.com/dapr/docs/blob/master/getting-started/environment-setup.md#installing-dapr-in-self-hosted-mode) to download and install the Dapr CLI and initialize Dapr.
|
||||
Follow [instructions](https://docs.dapr.io/getting-started/install-dapr/#install-dapr-in-self-hosted-mode) to download and install the Dapr CLI and initialize Dapr.
|
||||
|
||||
## Step 2 - Understand the Code
|
||||
|
||||
|
|
@ -148,11 +148,11 @@ To see that services have stopped running, run `dapr list`, noting that your ser
|
|||
|
||||
## Slim Init vs Default Init
|
||||
|
||||
With the run of `dapr init --slim`, only the binaries `daprd` and `placement` are installed in the system. In the normal default init, `dapr init` placement service is installed as a container and additionally redis and zipkin containers are run for enabling state store and tracing, which requires Docker to be installed as a prerequisite. See [environment setup](https://github.com/dapr/docs/blob/master/getting-started/environment-setup.md) for more information. The slim init provides only limited functionaity unless you [configure](https://github.com/dapr/docs/tree/master/howto/configure-redis#Self-Hosted-Mode-without-Containers) a state store yourself.
|
||||
With the run of `dapr init --slim`, only the binaries `daprd` and `placement` are installed in the system. In the normal default init, `dapr init` placement service is installed as a container and additionally redis and zipkin containers are run for enabling state store and tracing, which requires Docker to be installed as a prerequisite. See [environment setup](https://docs.dapr.io/getting-started/install-dapr/e) for more information. The slim init provides only limited functionaity unless you [configure](https://docs.dapr.io/getting-started/configure-redis/) a state store yourself.
|
||||
|
||||
|
||||
## Next Steps
|
||||
|
||||
Now that you've gotten Dapr running locally on your machine, consider these next steps:
|
||||
- Learn more about Dapr in the [Dapr overview](https://github.com/dapr/docs/blob/master/overview/README.md) documentation.
|
||||
- Explore Dapr concepts such as building blocks and components in the [Dapr concepts](https://github.com/dapr/docs/blob/master/concepts/README.md) documentation.
|
||||
- Learn more about Dapr in the [Dapr overview](https://docs.dapr.io/concepts/overview/) documentation.
|
||||
- Explore Dapr concepts such as building blocks and components in the [Dapr concepts](https://docs.dapr.io/concepts/) documentation.
|
||||
|
|
|
|||
|
|
@ -23,7 +23,7 @@ This sample requires you to have the following installed on your machine:
|
|||
|
||||
## Step 1 - Setup Dapr
|
||||
|
||||
Follow [instructions](https://github.com/dapr/docs/blob/master/getting-started/environment-setup.md#installing-dapr-in-self-hosted-mode) to download and install the Dapr CLI and initialize Dapr with `dapr init`.
|
||||
Follow [instructions](https://docs.dapr.io/getting-started/install-dapr/#install-dapr-in-self-hosted-mode) to download and install the Dapr CLI and initialize Dapr with `dapr init`.
|
||||
|
||||
## Step 2 - Understand the Code
|
||||
|
||||
|
|
@ -224,6 +224,6 @@ To see that services have stopped running, run `dapr list`, noting that your ser
|
|||
## Next Steps
|
||||
|
||||
Now that you've gotten Dapr running locally on your machine with state store, consider these next steps:
|
||||
- Learn more about Dapr in the [Dapr overview](https://github.com/dapr/docs/blob/master/overview/README.md) documentation.
|
||||
- Explore other Dapr concepts such as building blocks and components in the [Dapr concepts](https://github.com/dapr/docs/blob/master/concepts/README.md) documentation.
|
||||
- Learn more about Dapr in the [Dapr overview](https://docs.dapr.io/concepts/overview/) documentation.
|
||||
- Explore other Dapr concepts such as building blocks and components in the [Dapr concepts](https://docs.dapr.io/concepts/) documentation.
|
||||
- Look at other APIs available in the Dapr's [JavaScript SDK](https://github.com/dapr/js-sdk).
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ This tutorial walks you through the steps of setting up the OAuth middleware to
|
|||
|
||||
### Prerequisites
|
||||
|
||||
- [Dapr enabled Kubernetes cluster](https://github.com/dapr/docs/blob/master/getting-started/environment-setup.md#installing-dapr-on-a-kubernetes-cluster)
|
||||
- [Dapr enabled Kubernetes cluster](https://docs.dapr.io/getting-started/install-dapr/#install-dapr-on-a-kubernetes-cluster)
|
||||
- [Node.js version 8 or greater](https://nodejs.org/en/)
|
||||
- [Docker](https://docs.docker.com/)
|
||||
- [kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/)
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ This sample requires you to have the following installed on your machine:
|
|||
- [Docker](https://docs.docker.com/get-docker/)
|
||||
- [Dapr](https://github.com/dapr/cli/tree/release-0.10) v0.10.0+
|
||||
- [kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/)
|
||||
- A Kubernetes cluster, such as [Minikube](https://github.com/dapr/docs/blob/master/getting-started/cluster/setup-minikube.md), [AKS](https://github.com/dapr/docs/blob/master/getting-started/cluster/setup-aks.md) or [GKE](https://cloud.google.com/kubernetes-engine/)
|
||||
- A Kubernetes cluster, such as [Minikube](https://docs.dapr.io/operations/hosting/kubernetes/cluster/setup-minikube/), [AKS](https://docs.dapr.io/operations/hosting/kubernetes/cluster/setup-aks/) or [GKE](https://cloud.google.com/kubernetes-engine/)
|
||||
|
||||
Also, unless you have already done so, clone the repository with the samples and ````cd```` into the right directory:
|
||||
```
|
||||
|
|
@ -39,7 +39,7 @@ This should either have output as `No resources found in default namespace.` or
|
|||
|
||||
1. Setup Dapr
|
||||
|
||||
Follow [instructions](https://github.com/dapr/docs/blob/master/getting-started/environment-setup.md#environment-setup) to download and install the Dapr CLI and initialize Dapr.
|
||||
Follow [instructions](https://docs.dapr.io/getting-started/install-dapr/) to download and install the Dapr CLI and initialize Dapr.
|
||||
|
||||
2. Understand the code
|
||||
|
||||
|
|
@ -80,7 +80,7 @@ This simple gets the request, prints a log line and the request body in the cons
|
|||
cd ../deploy/
|
||||
```
|
||||
|
||||
The `kubernetes.yaml` file defines the component that Dapr has to register with the particular configuration. The binding spec can be seen [here](https://github.com/dapr/docs/blob/master/reference/specs/bindings/kubernetes.md).
|
||||
The `kubernetes.yaml` file defines the component that Dapr has to register with the particular configuration. The binding spec can be seen [here](https://docs.dapr.io/operations/components/setup-bindings/supported-bindings/kubernetes-binding/).
|
||||
|
||||
```yaml
|
||||
apiVersion: dapr.io/v1alpha1
|
||||
|
|
@ -261,7 +261,7 @@ kubectl apply -f ./deploy/kubernetes.yaml
|
|||
```
|
||||
|
||||
8. View the `./deploy/node.yaml` file. It does the following
|
||||
* Creates a role called `events-reader` with permission to `get, list and watch` `events` resource. More details can be found [here](https://github.com/dapr/docs/blob/master/reference/specs/bindings/kubernetes.md).
|
||||
* Creates a role called `events-reader` with permission to `get, list and watch` `events` resource. More details can be found [here](https://docs.dapr.io/operations/components/setup-bindings/supported-bindings/kubernetes-binding/).
|
||||
* Creates a role binding called `read-events` which binds default ServiceAccount in `kube-events` namespace to the Role previously created.
|
||||
* Create a service called `events-nodeapp`.
|
||||
* Creates a deployment called `events-nodeapp` with reference to be container created and pushed in steps 4 and 5.
|
||||
|
|
|
|||
|
|
@ -59,7 +59,7 @@ Twitter credentials will have to be added to `components/twitter.yaml`:
|
|||
|
||||
Starting from the root of demo 1 (`demos/demo1`)
|
||||
|
||||
* Install [Dapr CLI](https://github.com/dapr/docs/blob/master/getting-started/environment-setup.md#installing-dapr-cli)
|
||||
* Install [Dapr CLI](https://docs.dapr.io/getting-started/install-dapr/#install-the-dapr-cli)
|
||||
* Run
|
||||
|
||||
```sh
|
||||
|
|
|
|||
Loading…
Reference in New Issue