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

README: improve overview

Browse Source 
Signed-off-by: Solomon Hykes <sh.github.6811@hykes.org>
This commit is contained in:
Solomon Hykes 2021-03-29 23:53:38 +00:00
parent 37bd28711b
commit 9672fcb3c6
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
README.md
View File

@ -1,15 +1,16 @@
# Dagger # Dagger
Dagger is a platform for deploying your code using code. Dagger is a programmable deployment system.
Using Dagger, software builders can create powerful deployment workflows, tailor-made for their application, Using Dagger, software builders can automate the deployment of any application to any infrastructure,
in just a few lines of code. in just a few lines of code.
![image](https://user-images.githubusercontent.com/29565/112705398-d0222980-8e5b-11eb-98b9-32c117a3d606.jpeg) ![image](https://user-images.githubusercontent.com/29565/112705398-d0222980-8e5b-11eb-98b9-32c117a3d606.jpeg)
The Dagger platform adapts to your application, not the other way around.
The Dagger platform adapts to your application, not the other way around. Thanks to its vast ecosystem of reusable packages and flexible scripting system, Dagger can deploy virtually any Thanks to its ecosystem of reusable packages and flexible scripting system, Dagger can be dropped
application to any infrastructure, and integrate with any CI and build system. Think of it as your "devops superglu". 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. 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 This makes developers more productive, because they don't have to learn a new workflow every time their deployment