README
¶
What is Dagger?
Dagger is a tool that lets you replace your software project's artisanal scripts with a modern API and cross-language scripting engine.
- Encapsulate all your project's tasks and workflows into simple functions, written in your programming language of choice
- Dagger packages your functions into a custom GraphQL API
- Run your functions from the CLI, your language interpreter, or a custom HTTP client
- Package your functions into a module, to reuse in your next project or share with the community
- Search the Daggerverse for existing modules, and import them into yours. All Dagger modules can reuse each other's functions - across language.
Benefits to app teams
- Reduce complexity: even complex builds can be expressed as a few simple functions
- No more "push and pray": everything CI can do, your dev environment can do too
- Use the same language to develop your app and its scripts
- Easy onboarding of new developers: if you can build, test and deploy - they can too.
- Everything is cached by default: expect 2x to 10x speedups
- Parity between dev and CI environments
- Cross-team collaboration: reuse another team's workflows without learning their stack
Benefits to platform teams
- Reduce CI lock-in. Dagger functions run on all major CI platforms - no proprietary DSL needed.
- Don't be a bottleneck. Let app teams write their own functions. Enable standardization by providing them a library of reusable components.
- Faster CI runs. CI pipelines that are "Daggerized" typically run 2x to 10x faster, thanks to caching and concurrency. This means developers waste less time waiting for CI, and you spend less money on CI compute.
- A viable platform strategy. App teams need flexibility, and you need control. Dagger gives you a way to reconcile the two, in an incremental way that leverages the stack you already have.
Learn more
Join the community
- Join the Dagger community server
- Follow us on Twitter
- Come to a Dagger community call.
Contributing
Interested in contributing or building dagger from scratch? See CONTRIBUTING.md.
Directories
¶
| Path | Synopsis |
|---|---|
|
ci
module
|
|
|
std/go
Module
|
|
|
std/graphql
Module
|
|
|
std/shellcheck
Module
|
|
|
cmd
|
|
|
codegen/generator/go/templates
Go name linting.
|
Go name linting. |
|
dnsname
This is a post-setup plugin that establishes port forwarding - using iptables, from the host's network interface(s) to a pod's network interface.
|
This is a post-setup plugin that establishes port forwarding - using iptables, from the host's network interface(s) to a pod's network interface. |
|
otel-collector/loki
https://github.com/grafana/loki/blob/2dc5a71a6707383aadebe0b10c23c9e09c4f0ce7/integration/client/client.go
|
https://github.com/grafana/loki/blob/2dc5a71a6707383aadebe0b10c23c9e09c4f0ce7/integration/client/client.go |
|
ioctx
Package ioctx provides a way to pass standard input, output, and error streams through a context.Context.
|
Package ioctx provides a way to pass standard input, output, and error streams through a context.Context. |
|
dev
module
|
|
|
dirdiff
Module
|
|
|
go
Module
|
|
|
graphql
Module
|
|
|
markdown
Module
|
|
|
shellcheck
Module
|
|
|
wolfi
Module
|
|
|
docs
|
|
|
distconsts
Module
|
|
|
internal
|
|
|
distconsts
Package consts exists to facilitate sharing values between our CI infra and dependent code (e.g.
|
Package consts exists to facilitate sharing values between our CI infra and dependent code (e.g. |
|
mage
Module
|
|
|
modules
|
|
|
dirdiff
Module
|
|
|
gha
Module
|
|
|
go
Module
|
|
|
golangci
Module
|
|
|
graphql
Module
|
|
|
markdown
Module
|
|
|
ps-analyzer
Module
|
|
|
ruff
Module
|
|
|
shellcheck
Module
|
|
|
wolfi
Module
|
|
Click to show internal directories.
Click to hide internal directories.