🚀 Why Go 1.24?

🛠️ Key Features (Alpha v0.1.2)

🏗️ The Tech Stack

🔗 Check out the Repo

What's Next? As developers, we've all been there: you need to monitor your server, check Docker logs, or tweak a firewall rule, but you don't want to install a heavy, resource-hungry control panel that eats up 512MB of RAM just to stay idle. I decided to solve this by building Blackwater—a "ninja-level" server management tool designed to be fast, secure, and incredibly lightweight. When I started this project, I had one goal: Zero Bloat. Go was the obvious choice because: Blackwater isn't just another dashboard; it's a real-time management engine: Blackwater is currently in its early Alpha stage. I'm looking for fellow Gophers and DevOps enthusiasts to: I’d love to get your feedback (and maybe a ⭐️ if you like the concept!): GitHub: https://github.com/Ahmedfargh/black-water-server-manager I’m currently working on a Docker Compose UI and an automated Security Alert System that notifies the admin via email when a new login is detected. Templates let you quickly answer FAQs or store snippets for re-use. as well , this person and/or - Single Binary: Easy deployment without worrying about dependencies.

- Concurrency: Handling multiple WebSocket streams for live logs is a breeze with Goroutines.- Low Footprint: It runs perfectly even on the smallest Raspberry Pi or a $5 VPS. - Real-Time Metrics ($O(1)$ Broadcasting): I built a custom WebSocket Hub. It fetches system stats once and broadcasts them to all connected clients, ensuring minimal CPU overhead.- Docker Integration: Using the official Docker SDK for Go, you can inspect, start/stop containers, and stream live container logs directly.- Multi-Distro Firewall: Native support for both UFW and Firewalld. No matter your Linux distro, Blackwater has your back.- Process Ownership Tracking: It doesn't just list processes; it tracks who started what, making it great for shared environments. - Backend: Go 1.24 + Gin Gonic- Database: MySQL + GORM- Auth: JWT-based RBAC (Role-Based Access Control)- Real-time: WebSockets (Custom Hub Architecture) - Review the Command Sanitization logic for security.- Suggest improvements for the WebSocket Hub scaling.- Contribute to the upcoming Web UI.