dagger
aws-cdk
dagger | aws-cdk | |
---|---|---|
114 | 308 | |
13,901 | 12,240 | |
2.0% | 0.8% | |
9.9 | 10.0 | |
about 18 hours ago | about 1 hour ago | |
Go | TypeScript | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
dagger
-
DevOps in 2025: the future is automated, git-ified, and kinda scary but fun.
Pipelines-as-code with Tekton, GitHub Actions, or even Dagger
-
Docker Management Is Evolving These 8 Tools Made My Life Easier
1. Dagger — The CI/CD Brain Docker Always Wanted
- Dagger Shell: Unix Pipeline Pattern for Typed API Objects
-
The Pain That Is GitHub Actions
mise (https://mise.jdx.dev/) and dagger (https://github.com/dagger/dagger) seem like nice candidates too!
Mise can install all your deps, and run tasks
-
Python in DevOps: Automation, Efficiency, and Scalability
While YAML has been a traditional choice for defining pipelines, Python SDKs like Dagger provide developers with programmatic control. Instead of static files, you can write functions to configure, test, and deploy applications dynamically.
-
The DevOps Engineer's Handbook
uh-huh: https://github.com/earthly/earthly/blob/v0.8.15/LICENSE (MPLv2, just like TF used to be) https://github.com/dagger/dagger/blob/v0.15.2/LICENSE (Apache 2)
-
The CD Pipeline Manifesto
I commend anyone who’s taking a hard look at our current CI/CD practices. Good work! Succinctly stating the problems is easier said than done.
I believe https://dagger.io checks all these manifesto boxes and more. At least that’s where I’m focusing my attention.
-
SymfonyCon Vienna 2024: Recap of our Experience
A standout presentation came from Paul Dragoonis about Dagger, a programmable CI/CD engine created by the author of Docker, Solomon Hykes. The talk illustrated how PHP developers can leverage Dagger to define their CI/CD pipelines as code, creating and managing Docker containers programmatically, a significant step forward for PHP deployment automation.
-
Show HN: Glu – Deployment pipeline framework as code
I don't want to yuck your yum, since it seems like this solved your problem for your crew. However, I always value launch posts like this which have a "why not ..." section, since (a) it helps folks who want to adopt your toy to understand its tradeoffs and know if they are the right tradeoffs for the adopter (b) it shows that the system was at least plausibly well designed and not filled with "oh, is that a thing?!" which requires abandoning it shortly after stumbling on real problems (I think of this as "The JavaScript Framework Lifecycle")
For example, this sure does look like Dagger <https://github.com/dagger/dagger#what-is-dagger> in its use of golang-as-ci <https://docs.dagger.io/quickstart/daggerize#construct-a-pipe...> and plausibly "run ci locally"
Dagger doesn't ship with a dashboard (that I know of) but I also struggle to think of why one would want an artisanal dashboard when <https://docs.github.com/en/actions/use-cases-and-examples/de...> and <https://docs.gitlab.com/ee/ci/environments/index.html> exist in close proximity to the existing CI infrastructure. I guess if one is trying to be "CI agnostic" but my life experience is that trying to be CI agnostic leads to a lot of NIH which one cannot hire for and cannot take to the next job
-
Dagger 0.14
Looks like Dagger has a Rust SDK [0]! Going to give it a try.
[0] https://github.com/dagger/dagger/tree/main/sdk/rust
aws-cdk
-
AWS CDK in Action — May 2025: Empowered Deployments, Governance, and Community
Deepu Mohan Puthrote contributed OidcProviderNativeConstruct here. Thanks for working with the CDK team on getting this important feature in!
-
AWS CDK Logical ID Deep Dive: How Adding One CloudFront Origin Broke My Entire AWS CDK Deployment
This constraint is documented in the AWS CloudFormation documentation and has been reported in the AWS CDK community (Issue #34629). The AWS documentation for "Updating VPC Origins" explicitly describes this limitation.
-
Using AWS CDK Property Injectors
Property Injectors is a feature that allows you to centrally modify properties (props) for all instances of "specific types of L2 Constructs (including some L3 Constructs)" within an App, Stack, or Construct. This feature was introduced in AWS CDK v2.196.0.
-
☁️ Keep Using AWS as Usual
Move to CDK or SAM.
-
🚀 Let's use SAM: rebuilding our minimal serverless MCP server
Hey devs 👋, if you saw my first two post in this series about building a minimal Model Context Protocol server with AWS Lambda using the Serverless Framework, this is the natural follow-up for those who prefer using AWS Serverless Application Model (SAM).
-
Using Docker in AWS Amplify Builds: A Step-by-Step Guide
const cluster = new ecs.Cluster(stack, 'ECSCluster', { clusterName: 'ECSCluster', vpc: vpc, }); const taskDefinition = new ecs.FargateTaskDefinition(stack, 'TaskDefinition', { cpu: 4096, memoryLimitMiB: 16384, runtimePlatform: { cpuArchitecture: ecs.CpuArchitecture.X86_64, operatingSystemFamily: ecs.OperatingSystemFamily.LINUX, }, }) const dockerImageAsset = new DockerImageAsset(stack, 'DockerImageAsset', { directory: resolvePath('./docker'), platform: Platform.LINUX_AMD64, }); // see https://aws.amazon.com/blogs/aws/aws-fargate-enables-faster-container-startup-using-seekable-oci/ // and https://github.com/aws/aws-cdk/issues/26413 SociIndexBuild.fromDockerImageAsset(stack, 'Index', imageProcessorDockerImage); taskDefinition.addContainer('Container', { containerName: 'Container', image: ecs.ContainerImage.fromDockerImageAsset(imageProcessorDockerImage), essential: true, });
-
🚀 From Serverless Framework to AWS CDK: rebuilding our minimal serverless MCP server
Hey devs 👋, if you saw my last post about building a minimal Model Context Protocol server with AWS Lambda using the Serverless Framework, this is the natural follow-up for those who prefer using AWS CDK.
- Construyendo un sistema RAG para búsqueda y análisis de contenido de video
-
Automating Voicebot Deployments for Amazon Connect
“Dynamic” resources are those that change frequently as part of the voicebot release cycle, either directly influencing such changes or as a result of these. Amazon Lex bots and any AWS Lambda function associated with them, are considered dynamic resources. Due to its relationship with voicebot code, it’s better for them to live in the same code repository, and follow its same release process, preferably using a higher level IaC framework such as AWS SAM or AWS Cloud Development Kit (CDK).
-
Building a RAG System for Video Content Search and Analysis
While this notebook demonstrates the core functionality, implementing a demo solution requires a more robust architecture. To address this need, I've developed "Ask Your Video" - a complete serverless solution that you can deploy using AWS Cloud Development Kit (CDK) 😏.
What are some alternatives?
Bazel - a fast, scalable, multi-language and extensible build system
sst - Build full-stack apps on your own infrastructure.
earthly - Super simple build framework with fast, repeatable builds and an instantly familiar syntax – like Dockerfile and Makefile had a baby.
cdk8s - Define Kubernetes native apps and abstractions using object-oriented programming
Task - A task runner / simpler Make alternative written in Go
ts-node - TypeScript execution and REPL for node.js