kjuulh/dagger
Archived
1
0
Fork 0
Code Issues 1 Pull Requests 1 Projects Releases Wiki Activity

Docs: rewrite intro and "vs" to match landing page

Browse Source 
Signed-off-by: Solomon Hykes <solomon@dagger.io>
This commit is contained in:
Solomon Hykes
2021-12-07 21:39:49 +00:00
committed by Solomon Hykes
parent 4dd72b78a1
commit 79f86227f3
2 changed files with 31 additions and 47 deletions
Download Patch File Download Diff File Expand all files Collapse all files

31
docs/introduction/what_is.md
View File

@@ -4,32 +4,13 @@ slug: /
# What is Dagger?
Dagger is a universal deployment engine. Write your deployment logic once, run it securely from anywhere.
Dagger is a portable devkit for CICD. It helps you develop powerful CICD pipelines that can run anwyhere.
Key features:
* Escape YAML hell. Thanks to the Cue language, writing configuration is as fun and productive as writing code.
* A powerful declarative execution engine to automate even the most complex and custom logic
* Static type checking so you can catch configuration errors before running that huge deployment
* Built-in caching and parallelism for maximum scale and performance
* An ecosystem of reusable packages to save you time and share your expertise with the community
* Avoid CI lock-in: the same Dagger configuration can be used in any CI, or with no CI at all
* Rapid local development: test and run everything locally, in seconds.
* Deploy from CI or the laptop: no more duplicating your CI config in a Makefile just so you can perform a task locally.
* Native support for encrypted secrets
* Just-in-time artifacts: fetch, transform and produce any artifact on the fly: source repositories, container images, binaries, database exports, ML models...
Using Dagger, teams with different deployment workflows can more easily collaborate and deploy each other's software,
without being forced to change their tools.
Typical use cases:
* On-demand staging environments for reviewing code changes
* Manage CICD across multiple repositories and CI runners, with one unified configuration
* Iterate on infrastructure without disrupting development teams
* Lock down access to the production cluster so that only authorized configurations are applied
* Common ground between the PaaS, Kubernetes and Serverless siloes.
* On-demand integration environments for testing complex changes spanning several teams
* 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!
* 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.
* Test and debug your pipelines locally; catch configuration errors in seconds with static type checking.
![Dagger_Website_Ship](https://user-images.githubusercontent.com/216487/122216381-328a3500-ce61-11eb-907f-d2b6f66b3b10.png)