website: hardcode version banner for 0.1 docs
O.1 docs is deprecated. Let's inform user to switch the the latest version Signed-off-by: user.email <jf@dagger.io>
This commit is contained in:
user.email
@@ -1,6 +1,6 @@
|
||||
---
|
||||
slug: /1200/local-dev
|
||||
displayed_sidebar: europa
|
||||
displayed_sidebar: '0.2'
|
||||
---
|
||||
|
||||
# CI/CD in your local dev
|
||||
@@ -215,7 +215,7 @@ From a powershell terminal, run:
|
||||
Invoke-WebRequest -UseBasicParsing -Uri https://dl.dagger.io/dagger/install.ps1 | Invoke-Expression
|
||||
```
|
||||
|
||||
We'll save everything under `<your home folder>/dagger`
|
||||
We'll save everything under `<your home folder>/dagger`
|
||||
|
||||
Check that `dagger` is installed correctly by opening a `Command Prompt` terminal and run:
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
slug: /1201/ci-environment
|
||||
displayed_sidebar: europa
|
||||
displayed_sidebar: '0.2'
|
||||
---
|
||||
|
||||
# Integrating with your CI environment
|
||||
@@ -48,57 +48,56 @@ If you would like us to document CircleCI next, vote for it here: [dagger#1677](
|
||||
|
||||
```yaml
|
||||
.docker:
|
||||
image: docker:${DOCKER_VERSION}-git
|
||||
services:
|
||||
- docker:${DOCKER_VERSION}-dind
|
||||
variables:
|
||||
# See https://docs.gitlab.com/ee/ci/docker/using_docker_build.html#docker-in-docker-with-tls-enabled-in-the-docker-executor
|
||||
DOCKER_HOST: tcp://docker:2376
|
||||
image: docker:${DOCKER_VERSION}-git
|
||||
services:
|
||||
- docker:${DOCKER_VERSION}-dind
|
||||
variables:
|
||||
# See https://docs.gitlab.com/ee/ci/docker/using_docker_build.html#docker-in-docker-with-tls-enabled-in-the-docker-executor
|
||||
DOCKER_HOST: tcp://docker:2376
|
||||
|
||||
DOCKER_TLS_VERIFY: '1'
|
||||
DOCKER_TLS_CERTDIR: '/certs'
|
||||
DOCKER_CERT_PATH: '/certs/client'
|
||||
DOCKER_TLS_VERIFY: '1'
|
||||
DOCKER_TLS_CERTDIR: '/certs'
|
||||
DOCKER_CERT_PATH: '/certs/client'
|
||||
|
||||
# Faster than the default, apparently
|
||||
DOCKER_DRIVER: overlay2
|
||||
# Faster than the default, apparently
|
||||
DOCKER_DRIVER: overlay2
|
||||
|
||||
DOCKER_VERSION: '20.10'
|
||||
DOCKER_VERSION: '20.10'
|
||||
|
||||
.dagger:
|
||||
extends: [.docker]
|
||||
variables:
|
||||
DAGGER_VERSION: 0.2.4
|
||||
DAGGER_LOG_FORMAT: plain
|
||||
DAGGER_CACHE_PATH: .dagger-cache
|
||||
extends: [.docker]
|
||||
variables:
|
||||
DAGGER_VERSION: 0.2.4
|
||||
DAGGER_LOG_FORMAT: plain
|
||||
DAGGER_CACHE_PATH: .dagger-cache
|
||||
|
||||
ARGS: ''
|
||||
cache:
|
||||
key: dagger-${CI_JOB_NAME}
|
||||
paths:
|
||||
- ${DAGGER_CACHE_PATH}
|
||||
before_script:
|
||||
- apk add --no-cache curl
|
||||
- |
|
||||
# install dagger
|
||||
cd /usr/local
|
||||
curl -L https://dl.dagger.io/dagger/install.sh | sh
|
||||
cd -
|
||||
ARGS: ''
|
||||
cache:
|
||||
key: dagger-${CI_JOB_NAME}
|
||||
paths:
|
||||
- ${DAGGER_CACHE_PATH}
|
||||
before_script:
|
||||
- apk add --no-cache curl
|
||||
- |
|
||||
# install dagger
|
||||
cd /usr/local
|
||||
curl -L https://dl.dagger.io/dagger/install.sh | sh
|
||||
cd -
|
||||
|
||||
dagger version
|
||||
script:
|
||||
- dagger project update
|
||||
- |
|
||||
dagger \
|
||||
do \
|
||||
--cache-from type=local,src=${DAGGER_CACHE_PATH} \
|
||||
--cache-to type=local,mode=max,dest=${DAGGER_CACHE_PATH} \
|
||||
${ARGS}
|
||||
dagger version
|
||||
script:
|
||||
- dagger project update
|
||||
- |
|
||||
dagger \
|
||||
do \
|
||||
--cache-from type=local,src=${DAGGER_CACHE_PATH} \
|
||||
--cache-to type=local,mode=max,dest=${DAGGER_CACHE_PATH} \
|
||||
${ARGS}
|
||||
|
||||
build:
|
||||
extends: [.dagger]
|
||||
variables:
|
||||
ARGS: build
|
||||
|
||||
extends: [.dagger]
|
||||
variables:
|
||||
ARGS: build
|
||||
```
|
||||
|
||||
</TabItem>
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
slug: /1220/vs
|
||||
displayed_sidebar: europa
|
||||
displayed_sidebar: '0.2'
|
||||
---
|
||||
|
||||
# Dagger vs. Other Software
|
||||
@@ -9,16 +9,16 @@ displayed_sidebar: europa
|
||||
|
||||
Dagger does not replace your CI: it improves it by adding a portable development layer on top of it.
|
||||
|
||||
* Dagger runs on all major CI products. This *reduces CI lock-in*: you can change CI without rewriting all your pipelines.
|
||||
* Dagger also runs on your dev machine. This allows *dev/CI parity*: the same pipelines can be used in CI and development.
|
||||
- Dagger runs on all major CI products. This _reduces CI lock-in_: you can change CI without rewriting all your pipelines.
|
||||
- Dagger also runs on your dev machine. This allows _dev/CI parity_: the same pipelines can be used in CI and development.
|
||||
|
||||
## Dagger vs. PaaS (Heroku, Firebase, etc.)
|
||||
|
||||
Dagger is not a PaaS, but you can use it to add PaaS-like features to your CICD pipelines:
|
||||
|
||||
* A simple deployment abstraction for the developer
|
||||
* A catalog of possible customizations, managed by the platform team
|
||||
* On-demand staging or development environments
|
||||
- A simple deployment abstraction for the developer
|
||||
- A catalog of possible customizations, managed by the platform team
|
||||
- On-demand staging or development environments
|
||||
|
||||
Using Dagger is a good way to get many of the benefits of a PaaS (developer productivity and peace of mind),
|
||||
without giving up the benefits of custom CICD pipelines (full control over your infrastructure and tooling).
|
||||
@@ -29,15 +29,15 @@ Most applications have a custom deploy script that usually gets the job done, bu
|
||||
|
||||
Using Dagger, you have two options:
|
||||
|
||||
1. You can *replace* your script with a DAG that is better in every way: more features, more reliable, faster, easier to read, improve, and debug.
|
||||
2. You can *extend* your script by wrapping it, as-is, into a DAG. This allows you to start using Dagger right away, and worry about rewrites later.
|
||||
1. You can _replace_ your script with a DAG that is better in every way: more features, more reliable, faster, easier to read, improve, and debug.
|
||||
2. You can _extend_ your script by wrapping it, as-is, into a DAG. This allows you to start using Dagger right away, and worry about rewrites later.
|
||||
|
||||
## Dagger vs. Infrastructure as Code (Terraform, Pulumi, Cloudformation, CDK)
|
||||
|
||||
Dagger is the perfect complement to an IaC tool.
|
||||
|
||||
* IaC tools help infrastructure teams answer questions like: what is the current state of my infrastructure? What is its desired state? And how do I get there?
|
||||
* Dagger helps CICD teams answer question like: what work needs to be done to deliver my application, in what order, and how do I orchestrate it?
|
||||
- IaC tools help infrastructure teams answer questions like: what is the current state of my infrastructure? What is its desired state? And how do I get there?
|
||||
- Dagger helps CICD teams answer question like: what work needs to be done to deliver my application, in what order, and how do I orchestrate it?
|
||||
|
||||
It is very common for a Dagger configuration to integrate with at least one IaC tool.
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
slug: /
|
||||
displayed_sidebar: europa
|
||||
displayed_sidebar: '0.2'
|
||||
---
|
||||
|
||||
# Getting Started
|
||||
|
||||
Reference in New Issue
Block a user