33d5add54b
The API was a bit confusing with code mixing the usage of Deployment and DeploymentState. This change marks a clear separation: - Client is the only piece of code manipulating *Deployment - CLI commands can manipulate DeploymentState objects and pass them to Client Signed-off-by: Andrea Luzzardi <aluzzardi@gmail.com> |
||
---|---|---|
.github | ||
cmd | ||
dagger | ||
doc | ||
examples | ||
pkg | ||
stdlib | ||
tests | ||
.daggerignore | ||
.gitignore | ||
.golangci.yml | ||
doc.go | ||
Dockerfile | ||
go.mod | ||
go.sum | ||
LICENSE | ||
Makefile | ||
README.md | ||
tracing.compose.yaml |
Dagger
Dagger is a programmable deployment system.
Using Dagger, software builders can automate the deployment of any application to any infrastructure, in just a few lines of code.
The Dagger platform adapts to your application, not the other way around. Thanks to its ecosystem of reusable packages and flexible scripting system, Dagger can be dropped into any software project without requiring changes to its architecture or workflow. Think of it as your "devops superglu".
No matter how your deployment works under the hood, you can manage it with the same Dagger user interface. This makes developers more productive, because they don't have to learn a new workflow every time their deployment system changes.
Examples
- Deploy a simple React application
- Deploy an application to your Kubernetes cluster
- Provision a Kubernetes cluster on AWS
- Add HTTP monitoring to your application
- Deploy an application to your Kubernetes cluster
Alpha disclaimer
Dagger is alpha-quality software. It has many bugs, the user interface is minimal, and it may change in incompatible ways at any time. If you are still willing to try it, thank you! We appreciate your help and encourage you to ask questions and report issues.