digger
AFNetworking
DISCONTINUED
Our great sponsors
digger | AFNetworking | |
---|---|---|
84 | 1 | |
2,617 | 33,351 | |
5.9% | - | |
9.9 | 0.0 | |
6 days ago | about 1 year ago | |
Go | Objective-C | |
Apache License 2.0 | MIT License |
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.
digger
-
GitHub issues from top Open Source Golang Repositories that you should contribute to
I would be extremely grateful if you could give us a star & share your thoughts in the comments section below https://github.com/diggerhq/digger
-
Tools used by the top 1% of Platform Engineers and their Commercial Open Source Alternatives
Check Digger's repo on GitHub
-
5 Open Source tools written in Golang that you should know about
Digger is an Open Source Infrastructure as Code management tool that helps orchestrate IaC such as Terraform & OpenTofu within GitHub Actions. Digger reuses compute used for application code so that you don't overpay for 3rd party managed compute for IaC. This approach eliminates the duplication of CI/CD infrastructure such as compute, jobs, and logs, and reduces security concerns by keeping sensitive data within the CI job. Digger's integration with existing CI systems offers scalability by leveraging on-demand compute resources and enhances security by confining data within the existing CI environment.
-
Top 10 terraform tools you should know about.
Digger is an Open Source IaC management platform that allows you to orchestrate terraform/OpenTofu in your CI/CD system. It helps you resue async jobs infrastructure with compute, orchestration, logs, etc of your existing CI. Digger also has a pro version built on top of Digger’s community edition. Digger’s “bring your own compute” ensures that users have private runners by defualt and don’t have to pay for it additionally. Digger pro gives team leads, managers and IaC practitioners dashboards, Drift Detection, RBAC via OPA policies and concurrency so they can help guide the team.
-
OpenTF Announces Fork of Terraform
- https://digger.dev/ - https://github.com/diggerhq
-
OpenTerraform – an MPL fork of Terraform after HashiCorp's license change
To copy the comment from Reddit https://old.reddit.com/r/Terraform/comments/15o9mzt/openterr...
> Funny enough, our own product (Digger, an open-source CI runner for Terraform) is not using Terraform (or any other Hashicorp's code) under the hood.
Oh yes you are:
https://github.com/diggerhq/digger/blob/develop/pkg/core/ter...
You're on thin ice if you want to argue whether forking a terraform process constitutes "hosting" or "embedding" terraform.
We are in some sense a competitor too, alongside Spacelift, Env0, Scalr and a few others. Our product is built differently though, Digger is orchestrating terraform jobs in your existing CI instead of taking over the whole CI stack and effectively duplicating it just to run terraform. We built it this way almost by accident; our original product was very different (think "heroku-like UI for AWS" that generated and ran terraform on the server) and this is how we arrived at what Digger is now. Luckily we don't seem to be affected by the licensing change as we neither embed nor distribute any of hashicorp's code (it's on the user to set up the right version of it in say GH Actions).
https://github.com/diggerhq/digger
Anyways, fully agree that if you have a great product, you don't need to make such moves. We designed our product the way we did purely out of technical considerations - it didn't seem to make any sense to duplicate the CI stack. But it looks like this whole idea behind Terraform Cloud of having an "infra-specific CI" was driven exclusively by commercial interest. You can charge per minute! You can charge even more per resource! Now it's catching up with Hashi; so they have to make such defensive moves. If the product made sense technically, if it was designed the way someone would design it with no commercial considerations whatsoever, they wouldn't have to make such moves.
- FLaNK Stack Weekly for 17 July 2023
-
Terraform Tower
Digger
One of the founders of Digger here (thanks everyone for mentioning us!) We are an open-source CI/CD tool for Terraform - just like Ansible Tower
AFNetworking
-
Awesome macOS Libraries List
AFNetworking - A delightful networking framework. Language: Objective-C.
What are some alternatives?
Alamofire - Elegant HTTP Networking in Swift
Moya - Network abstraction layer written in Swift.
atlantis - Terraform Pull Request Automation
CocoaAsyncSocket - Asynchronous socket networking library for Mac and iOS
RestKit - RestKit is a framework for consuming and modeling RESTful web resources on iOS and OS X
terrakube - Open source IaC Automation and Collaboration Software.
ASIHTTPRequest - Easy to use CFNetwork wrapper for HTTP requests, Objective-C, Mac OS X and iPhone
apollo-ios - 📱 A strongly-typed, caching GraphQL client for iOS, written in Swift.
Netfox - A lightweight, one line setup, iOS / OSX network debugging library! 🦊
Reachability.swift - Replacement for Apple's Reachability re-written in Swift with closures
protobuf-swift - Google ProtocolBuffers for Apple Swift
HappyDns - dns library for objective c