90DaysOfDevOps
This repository started out as a learning in public project for myself and has now become a structured learning map for many in the community. We have 3 years under our belt covering all things DevOps, including Principles, Processes, Tooling and Use Cases surrounding this vast topic.
About 90DaysOfDevOps
This repository started out as a learning in public project for myself and has now become a structured learning map for many in the community. We have 3 years under our belt covering all things DevOps, including Principles, Processes, Tooling and Use Cases surrounding this vast topic.
What you should know about 90DaysOfDevOps
90DaysOfDevOps — This repository started out as a learning in public project for myself and has now become a structured learning map for many in the community. We have 3 years under our belt covering all things DevOps, including Principles, Processes, Tooling and Use Cases surrounding this vast topic.. It is categorized under DevOps and primarily built with Shell. The project has gathered 29,423 stars and 6,726 forks on GitHub, indicating strong adoption among developers.
Pricing & licensing: This tool is offered free of charge , released under the Unknown license. The source code is openly available on GitHub, allowing engineers to audit, contribute, or fork as needed.
Use cases & topics: 90DaysOfDevOps is associated with the following topics: ansible, backup, containers, devops, iac, kubernetes, networking, terraform. Teams working in ansible / backup / containers spaces typically evaluate this kind of tool when scoping new architecture decisions or replacing legacy components.
Getting started: Check out the official GitHub repository for installation steps, configuration examples, and the latest release notes. Most teams hit value within the first week if the tool aligns with their existing DevOps stack.
Editor's note from Fanny Engriana (Founder, Wardigi Digital Agency): when evaluating tools in the DevOps category for our agency clients, we look at three things first — license clarity, community size, and active maintenance. Tools with explicit license terms and ongoing commits tend to remain viable across multi-year projects.