
Excited to share the latest feature built for Gubernator (gbnt): Visual Stack Topology &...
Gubernator is designed as a "Goldilocks" orchestrator—combining the raw simplicity of Docker Compose with Nomad-inspired scheduling and hardware/AI targeting. But deploying complex multi-container stacks means visualization is key to maintaining control.
To bridge this gap, I’ve just integrated a native Web Network Schema & Container Topology Viewer directly into the Gubernator dashboard:

What makes it unique?
Auto-discovered Ingress & Routing: The scheduler parses docker-compose.yml to automatically place a virtual Caddy Ingress node in web-facing services (e.g. n8n, WordPress, Jupyter) and internal sinks/databases (e.g. MySQL, PostgreSQL).
Live Network Context: Every container card details live telemetry—including internal container IPs, host port mappings, and active domains (e.g.ingress.host).
Visual Dependency Mapping: Custom Bézier-curve connection lines are dynamically drawn in yellow/amber to highlight container network relationships and dependencies (like depends_on).

One-Click Multi-Format Export: Perfect for team architecture syncs or DevOps documentation! Diagrams can be instantly exported and downloaded as PNG, JPEG, PDF, or native SVG (automatically adapting to light/dark system themes).
Gubernator continues its journey to simplify local and edge container orchestration. Let me know what you think of this visualization layer!
https://github.com/mario-ezquerro/gubernator/
_ #Docker #Golang #Flutter #DevOps #Nomad #Orchestration #WebDevelopment #SystemArchitecture #Containers
aiMost of us have seen a coding agent fail to complete a task we know it can do. We just don't...
googlecloudWhen building Generative AI applications, developers often encounter a massive bottleneck: sequential...
discussI’ve been thinking about sharing some electronic circuit posts on Dev.to — small circuits, DIY...
agentsWhat nobody tells you about exporting your multi-agent prototype to a local workspace. Every...
agenticarchitectAutonomous agents are genuinely good at answering messy business questions. Give one an LLM and a set...
aiPR volume went up, ticket quality didn't, and the gap got filled with LLMs on both sides of the review: bots reviewing, bots replying, bots occasionally arguing with bots about priorities that only existed in a teammate's head. Our CEO named the actual problem, and it's bigger than code review.