docs: Correctly capitalize GitHub
Signed-off-by: Issy Long <me@issyl0.co.uk>
This commit is contained in:
parent
5757a28412
commit
13d6a8370f
@ -5,7 +5,7 @@ displayed_sidebar: europa
|
|||||||
|
|
||||||
# Dagger vs. Other Software
|
# Dagger vs. Other Software
|
||||||
|
|
||||||
## Dagger vs. CI (Github Actions, Gitlab, CircleCI, Jenkins, etc.)
|
## Dagger vs. CI (GitHub Actions, Gitlab, CircleCI, Jenkins, etc.)
|
||||||
|
|
||||||
Dagger does not replace your CI: it improves it by adding a portable development layer on top of it.
|
Dagger does not replace your CI: it improves it by adding a portable development layer on top of it.
|
||||||
|
|
||||||
|
@ -9,7 +9,7 @@ Dagger is a portable devkit for CICD. It helps you develop powerful CICD pipelin
|
|||||||
* Choose from a wide catalog of reusable actions, or create your own in your favorite programming language.
|
* Choose from a wide catalog of reusable actions, or create your own in your favorite programming language.
|
||||||
* Tie it all together with [CUE](https://cuelang.org), the next-generation declarative language invented at Google. No more YAML hell!
|
* Tie it all together with [CUE](https://cuelang.org), the next-generation declarative language invented at Google. No more YAML hell!
|
||||||
* Unify dev and CI. The same Dagger pipeline can run on your dev machine or in CI. All you need is a Docker-compatible runtime.
|
* Unify dev and CI. The same Dagger pipeline can run on your dev machine or in CI. All you need is a Docker-compatible runtime.
|
||||||
* Avoid CI lock-in. Dagger runs natively on Github Actions, Gitlab, CircleCI, Jenkins, AWS Codebuild, Tekton, and more.
|
* Avoid CI lock-in. Dagger runs natively on GitHub Actions, Gitlab, CircleCI, Jenkins, AWS Codebuild, Tekton, and more.
|
||||||
* Test and debug your pipelines locally; catch configuration errors in seconds with static type checking.
|
* Test and debug your pipelines locally; catch configuration errors in seconds with static type checking.
|
||||||
|
|
||||||
<img src="/img/what-is-dagger.png" alt="Dagger_Website_Ship" style={{maxWidth: '50%'}} />
|
<img src="/img/what-is-dagger.png" alt="Dagger_Website_Ship" style={{maxWidth: '50%'}} />
|
||||||
|
@ -4,7 +4,7 @@ slug: /1002/vs/
|
|||||||
|
|
||||||
# Dagger vs. Other Software
|
# Dagger vs. Other Software
|
||||||
|
|
||||||
## Dagger vs. CI (Github Actions, Gitlab, CircleCI, Jenkins, etc.)
|
## Dagger vs. CI (GitHub Actions, Gitlab, CircleCI, Jenkins, etc.)
|
||||||
|
|
||||||
Dagger does not replace your CI: it improves it by adding a portable development layer on top of it.
|
Dagger does not replace your CI: it improves it by adding a portable development layer on top of it.
|
||||||
|
|
||||||
|
@ -2,26 +2,26 @@
|
|||||||
slug: /1009/github-actions/
|
slug: /1009/github-actions/
|
||||||
---
|
---
|
||||||
|
|
||||||
# Integrate Dagger with Github Actions
|
# Integrate Dagger with GitHub Actions
|
||||||
|
|
||||||
This tutorial illustrates how to use Github Actions and Dagger to build, push and deploy Docker images to Cloud Run.
|
This tutorial illustrates how to use GitHub Actions and Dagger to build, push and deploy Docker images to Cloud Run.
|
||||||
|
|
||||||
## Prerequisites
|
## Prerequisites
|
||||||
|
|
||||||
We assume that you've finished our 106-cloudrun tutorial as this one continues right after.
|
We assume that you've finished our 106-cloudrun tutorial as this one continues right after.
|
||||||
|
|
||||||
## Setup new Github repo
|
## Setup new GitHub repo
|
||||||
|
|
||||||
Push existing `examples/todoapp` directory to your new Github repo (public or private). It should contain all the code
|
Push existing `examples/todoapp` directory to your new GitHub repo (public or private). It should contain all the code
|
||||||
from `https://github.com/dagger/examples/tree/main/todoapp`, `gcpcloudrun` and `.dagger/env/gcpcloudrun/` directory.
|
from `https://github.com/dagger/examples/tree/main/todoapp`, `gcpcloudrun` and `.dagger/env/gcpcloudrun/` directory.
|
||||||
|
|
||||||
### Add Github Actions Secret
|
### Add GitHub Actions Secret
|
||||||
|
|
||||||
Dagger encrypts all input secrets using your key stored at `~/.config/dagger/keys.txt`. Copy the entire line starting
|
Dagger encrypts all input secrets using your key stored at `~/.config/dagger/keys.txt`. Copy the entire line starting
|
||||||
with `AGE-SECRET-KEY-` and save it to a Github secret named `DAGGER_AGE_KEY`. In case you don't know how to create
|
with `AGE-SECRET-KEY-` and save it to a GitHub secret named `DAGGER_AGE_KEY`. In case you don't know how to create
|
||||||
secrets on Github take a look at [this tutorial](https://docs.github.com/en/actions/reference/encrypted-secrets).
|
secrets on GitHub take a look at [this tutorial](https://docs.github.com/en/actions/reference/encrypted-secrets).
|
||||||
|
|
||||||
## Create a Github Actions Workflow
|
## Create a GitHub Actions Workflow
|
||||||
|
|
||||||
Create `.github/workflows/gcpcloudrun.yml` file and paste the following code into it:
|
Create `.github/workflows/gcpcloudrun.yml` file and paste the following code into it:
|
||||||
|
|
||||||
|
@ -58,7 +58,7 @@ To install it just run
|
|||||||
dagger mod get github.com/dagger/packages/gcpcloudrun@v0.1
|
dagger mod get github.com/dagger/packages/gcpcloudrun@v0.1
|
||||||
```
|
```
|
||||||
|
|
||||||
It should pull the `v0.1` version from Github, leave a copy in `cue.mod/pkg` and reflect the change in
|
It should pull the `v0.1` version from GitHub, leave a copy in `cue.mod/pkg` and reflect the change in
|
||||||
`cue.mod/dagger.mod` file:
|
`cue.mod/dagger.mod` file:
|
||||||
|
|
||||||
```shell
|
```shell
|
||||||
|
@ -60,7 +60,7 @@ This is what the above looks like in the Dagger plan config:
|
|||||||
|
|
||||||
```
|
```
|
||||||
|
|
||||||
## Github Action integration
|
## GitHub Action integration
|
||||||
|
|
||||||
This is the GitHub Actions workflow config that invokes `dagger`, which in turn runs the full plan:
|
This is the GitHub Actions workflow config that invokes `dagger`, which in turn runs the full plan:
|
||||||
|
|
||||||
|
Reference in New Issue
Block a user