|**[Getting Started](getting_started.md)** | Set up your development environment.
|**[Frontend Backend Run Example](frontend_backend_run.md)** | Learn how to run an application locally with tye.
|**[Frontend Backend Deploy Example](frontend_backend_deploy.md)** | Learn how to deploy an application with tye.
|**[Adding Redis](redis.md)** | Learn how to add redis for development and deployed to a development cluster.
|**[Getting Started](getting_started.md)** | Get setup to develop with `tye`.
|**[Basic Tutorial (run locally)](/docs/tutorials/hello-tye/00_run_locally.md)** | Learn how to run an application locally with `tye`.
|**[Basic Tutorial (deploy)](/docs/tutorials/hello-tye/01_deploy.md.md)** | Learn how to deploy an application with `tye`.
|**[Basic Tutorial (add Redis)](/docs/tutorials/hello-tye/02_add_redis.md)** | Learn how to add redis for development and deployed to a development cluster.
## Recipes
| Topic | Description|
|-------|------------|
|**[Using Dapr with Tye](recipes/dapr.md)** | Using Tye for local development and deployment with a [Dapr](https://dapr.io) application.
|**[Using Dapr with Tye](recipes/dapr.md)** | Using `tye` for local development and deployment with a [Dapr](https://dapr.io) application.
## Reference documentation
@ -22,5 +22,5 @@
| Area | Description |
|------|-------------|
|**[Tye Commandline Reference](reference/commandline/README.md)** | Documentation for `tye` commands.
|**[Service Discovery](service_discovery.md)** | Learn more about service discovery in tye.
**:warning: The current Dapr dotnet-sdk release has an issue where its default settings don't work when deployed with mTLS enabled. This will be resolved as part of the upcoming 0.6.0 release. For now you can work around this by disabling mTLS as part of Dapr installation.**
First, you will need a Kubernetes instance to deploy to. The [Frontend-Backed Deployment tutorial](/docs/frontend_backend_deploy.md) covers some options.
First, you will need a Kubernetes instance to deploy to. The [Basic Tutorial](/docs/tutorials/hello-tye/01_deploy.md) covers some options.
Secondly initialize Dapr for your cluster following the instructions [here](https://github.com/dapr/samples/tree/master/2.hello-kubernetes). Make sure to configure redis as both a state store and as pub-sub as described [here](https://github.com/dapr/docs/blob/master/howto/configure-redis/README.md#configuration).
This tutorial will demonstrate how to use [`tye run`](/docs/reference/commandline/tye-run.md) to run a multi-project application. If you haven't so already, follow the [Getting Started Instructions](getting_started.md) to install tye.
This tutorial will demonstrate how to use [`tye run`](/docs/reference/commandline/tye-run.md) to run a multi-project application. If you haven't so already, follow the [Getting Started Instructions](/docs/getting_started.md) to install tye.
## Running a single application with tye run
@ -63,7 +63,7 @@ This tutorial will demonstrate how to use [`tye run`](/docs/reference/commandlin
## Getting the frontend to communicate with the backend
Now that we have two applications running, let's make them communicate. By default, `tye` enables service discovery by injecting environment variables with a specific naming convention. For more information on, see [service discovery](service_discovery.md).
Now that we have two applications running, let's make them communicate. By default, `tye` enables service discovery by injecting environment variables with a specific naming convention. For more information on, see [service discovery](/docs/service_discovery.md).
1. Add a NuGet.config to add the `dotnet-core` package source.
@ -220,4 +220,4 @@ Now that we have two applications running, let's make them communicate. By defau
## Next Steps
Now that you are able to run a multi-project application with [`tye run`](/docs/reference/commandline/tye-run.md), move on to the [Frontend Backend Deploy Sample](frontend_backend_deploy.md) to learn how to deploy this application to Kubernetes.
Now that you are able to run a multi-project application with [`tye run`](/docs/reference/commandline/tye-run.md), move on to [the next step (deploy)](01_deploy.md) to learn how to deploy this application to Kubernetes.
This tutorial assumes that you have completed the [Frontend Backend Run Sample](frontend_backend_run.md)
This tutorial assumes that you have completed the [first step (run locally)](00_run_locally.md)
> :bulb: `tye` will use your current credentials for pushing Docker images and accessing kubernetes clusters. If you have configured kubectl with a context already, that's what [`tye deploy`](/docs/reference/commandline/tye-deploy.md) is going to use!
@ -136,4 +136,4 @@ Tye has a optional configuration file (`tye.yaml`) to allow customizing settings
## Next Steps
Now that you are able to deploy an application to Kubernetes, learn how to add a non-project dependency to tye with our [Redis](redis.md) tutorial.
Now that you are able to deploy an application to Kubernetes, learn how to add a non-project dependency to tye with [the next step (add Redis)](02_add_redis.md).
This tutorial assumes that you have completed the [Frontend Backend Run Sample](frontend_backend_run.md) and [Frontend Backend Deploy Sample](frontend_backend_deploy.md).
This tutorial assumes that you have completed the [first step (run locally)](00_run_locally.md) and [second step (deploy)](01_deploy.md).
We just showed how `tye` makes it easier to communicate between 2 applications running locally but what happens if we want to use redis to store weather information?