122 lines
3.1 KiB
Markdown
122 lines
3.1 KiB
Markdown
# Dagger Examples
|
|
|
|
All example commands should be executed in the `examples/` directory
|
|
in an up-to-date checkout of the [dagger repository](https://github.com/dagger/dagger).
|
|
|
|
## Deploy a simple React application
|
|
|
|
This example shows how to deploy an example React Application. [Read the deployment plan](https://github.com/dagger/dagger/tree/main/examples/react)
|
|
|
|
Audience: Javascript developers looking to deploy their application.
|
|
|
|
Components:
|
|
|
|
- [Netlify](https://netlify.com) for application hosting
|
|
- [Yarn](https://yarnpkg.com) for building
|
|
- [Github](https://github.com) for source code hosting
|
|
- [React-Todo-App](https://github.com/kabirbaidhya/react-todo-app) by Kabir Baidhya as a sample application.
|
|
|
|
1. Change the current directory to the example deployment plan
|
|
|
|
```sh
|
|
cd ./react
|
|
```
|
|
|
|
2. Create a new deployment from the plan
|
|
|
|
```sh
|
|
dagger new
|
|
```
|
|
|
|
3. Configure the deployment with your Netlify access token.
|
|
You can create new tokens from the [Netlify dashboard](https://app.netlify.com/user/applications/personal).
|
|
|
|
```sh
|
|
dagger input text www.account.token MY_TOKEN
|
|
```
|
|
|
|
*NOTE: there is a dedicated command for encrypted secret inputs, but it is
|
|
not yet implemented. Coming soon!*
|
|
|
|
4. Deploy!
|
|
|
|
```sh
|
|
dagger up
|
|
```
|
|
|
|
|
|
## Provision a Kubernetes cluster on AWS
|
|
|
|
This example shows how to provision a new Kubernetes cluster on AWS, and configure your `kubectl` client to use it. [Read the deployment plan](https://github.com/dagger/dagger/tree/main/examples/kubernetes-aws)
|
|
|
|
Audience: infrastructure teams looking to provisioning kubernetes clusters as part of automated CICD pipelines.
|
|
|
|
Components:
|
|
|
|
- [Amazon EKS](https://aws.amazon.com/eks) for Kubernetes hosting
|
|
- [Amazon CloudFormation](https://aws.amazon.com/cloudformation) for infrastructure provisioning
|
|
- [Kubectl](https://kubernetes.io/docs/tasks/tools/#kubectl) as kubernetes client
|
|
|
|
1. Change the current directory to the example deployment plan
|
|
|
|
```sh
|
|
cd ./kubernetes-aws
|
|
```
|
|
|
|
2. Create a new deployment from the plan
|
|
|
|
```sh
|
|
dagger new
|
|
```
|
|
|
|
3. Configure the deployment with your AWS credentials
|
|
|
|
```sh
|
|
dagger input text awsConfig.accessKey MY_AWS_ACCESS_KEY
|
|
```
|
|
|
|
```sh
|
|
dagger input text awsConfig.secretKey MY_AWS_SECRET_KEY
|
|
```
|
|
|
|
|
|
4. Deploy!
|
|
|
|
```sh
|
|
dagger up
|
|
```
|
|
|
|
5. Export the generated kubectl config
|
|
|
|
```sh
|
|
dagger query kubeconfig.kubeconfig | jq . > kubeconfig
|
|
```
|
|
|
|
## aws-monitoring: HTTP Monitoring on AWS
|
|
|
|
This example implements a full HTTP(s) Monitoring solution on AWS using
|
|
Cloudformation and Cloudwatch Synthetics.
|
|
|
|
How to run:
|
|
|
|
```sh
|
|
dagger compute ./aws-monitoring \
|
|
--input-string awsConfig.accessKey="MY_AWS_ACCESS_KEY" \
|
|
--input-string awsConfig.secretKey="MY_AWS_SECRET_KEY" \
|
|
```
|
|
|
|
## kubernetes: Deploy to an existing Kubernetes cluster
|
|
|
|
This example shows two different ways for deploying to an existing Kubernetes
|
|
(EKS) cluster: a simple deployment spec (written in Cue), and a local helm
|
|
chart.
|
|
|
|
How to run:
|
|
|
|
```sh
|
|
dagger compute ./kubernetes \
|
|
--input-string awsConfig.accessKey="MY_AWS_ACCESS_KEY" \
|
|
--input-string awsConfig.secretKey="MY_AWS_SECRET_KEY" \
|
|
--input-dir helmChart.chart=./kubernetes/testdata/mychart
|
|
```
|