DoAct 2.0 is now an Official Community tool on DigitalOcean 🚀

I am extremely delighted to share with you that one of my recent projects, DoAct, got published as an #official community tool on one of the biggest cloud providers DigitalOcean. The project was under review by the Digital Ocean team and finally, they approved it.
I am very glad to see that the project is #trending on the very first page.

Now you can host your own runner on #DigitalOcean more easily to run jobs in your #GitHub Actions workflows and automate all your software workflows, now with world-class CI/CD. Build, test, and deploy your code right from GitHub.🚀

Links:

GitHub: https://github.com/itsksaurabh/doact

DigitalOcean: https://www.digitalocean.com/community/tools/doact

#digitalocean #community #devops #cicd #terraform #opensource

https://redd.it/gfslcc
@r_devops

Fluent Bit 3.0!

📷 Exciting News: Fluent Bit 3.0 is Here! 📷 A serious advancement for cloud native #observability teams, with new features and enhancements to power your telemetry needs and keep you in control of your data. #OpenSource


Read more on the u/Calyptia blog: https://calyptia.com/blog/fluent-bit-v3

https://redd.it/1bo7zeu
@r_devops

Introducing VPS Pilot – My open-source project to manage and monitor VPS servers!

 Built with:

Agents (Golang) installed on each VPS

Central server (Golang) receiving metrics via TCP

Dashboard (React.js) for real-time charts

TimescaleDB for storing historical data

 Features so far:

CPU, memory, and network monitoring (5m to 7d views)

Discord alerts for threshold breaches

Live WebSocket updates to the dashboard

 Coming soon:

Project management via config.vpspilot.json

Remote command execution and backups

Cron job management from central UI

 Looking for contributors!
If you're into backend, devops, React, or Golang — PRs are welcome 
 GitHub: https://github.com/sanda0/vps\_pilot

\#GoLang \#ReactJS \#opensource \#monitoring \#DevOps See less

https://redd.it/1kewtsx
@r_devops

🚀 Milestone Unlocked: 2K Stars! 🌟

🚀 Milestone Unlocked: 2K Stars! 🌟

My Cheat-Sheet Collection just hit 2,000 stars on GitHub!
Huge thanks to everyone who starred, shared, and contributed. Your support keeps this project growing. 🙌

If you haven't checked it out yet — it's a curated collection of high-quality PDF cheat sheets for developers, DevOps engineers, and tech enthusiasts. 📚💻

Feel free to explore, contribute, and share!
\#DevOps #CheatSheet #GitHub #OpenSource #Infosec #DevSecOps #Kubernetes #Linux

https://redd.it/1kuxk2d
@r_devops

#devops #infrastructureascode #kvm #virtualization #opensource #linux #automation #cloudnative #techinnovation #github #virsh #bash #terraform #kickstart #qemu #kvm | Ahmad M Waddah

Check KVMSpinUps

https://redd.it/1qbyxld
@r_devops

Terraform AWS Infrastructure Framework (Multi-Env, Name-Based, Scales by Config)

🚀 Excited to share my latest open-source project: a Terraform framework for AWS focused on multi-environment infrastructure management.

After building and refining patterns across multiple environments, I open-sourced a framework that helps teams keep deployments consistent across dev / qe / prod.

The problem:
- Managing AWS infra across dev / qe / prod usually leads to:
- Configuration drift between environments
- Hardcoded resource IDs everywhere
- Repetitive boilerplate when adding “one more” resource
- Complex dependency management across modules

The solution:
A workspace-based framework with automation:

- ✅ Automatic resource linking — reference resources by name, not IDs. The framework resolves and injects IDs automatically across modules.
- ✅ DRY architecture — one codebase for dev / qe / prod using Terraform workspaces.
- ✅ Scale by configuration, not code — create unlimited resources WITHOUT re-calling modules. Just add entries in a .tfvars file using plain-English names (e.g., “prod_vpc”, “private_subnet_az1”, “eks_cluster_sg”).

What’s included:
- VPC networking (multi-AZ, public/private subnets)
- Internet gateway, NAT gateway, route tables, EIPs
- Security groups + SG-to-SG references
- VPC endpoints (Gateway & Interface)
- EKS cluster + managed node groups

Real example:
# terraform.tfvars (add more entries, no new module blocks)
eks_clusters = {
prod = {
my_cluster = {
cluster_version = "1.34"
vpc_name = "prod_vpc" # name, not ID
subnet_name = ["pri_sub1", "pri_sub2"] # names, not IDs
sg_name = ["eks_cluster_sg"] # name, not ID
}
}
}
# Framework injects vpc_id, subnet_ids, sg_ids automatically

GitHub:
https://github.com/rajarshigit2441139/terraform-aws-infrastructure-framework

Looking for:
- Feedback from the community
- Contributors interested in IaC patterns
- Teams standardizing AWS deployments

Question:
What are your biggest challenges with multi-environment Terraform? How do you handle cross-module references today?

#Terraform #AWS #InfrastructureAsCode #DevOps #CloudEngineering #EKS #Kubernetes #OpenSource #CloudArchitecture #SRE

https://redd.it/1qkjko7
@r_devops