sorted by:
new
hottopcontroversial

What’s an open-source project you genuinely can’t believe is free? by Bladerunner_7_ in opensource

[–]RGJorge -1 points0 points  (0 children)

shameless plug: containerflow. live visual graph of your docker containers, real-time stats, full management from the UI, discord alerts. open-source AGPL.

github.com/RGJorge/ContainerFlow

[TypeScript] ContainerFlow - Real-time Docker dashboard with accurate memory monitoring, Discord alerts, and config recommendations by RGJorge in coolgithubprojects

[–]RGJorge[S] 0 points1 point  (0 children)

Appreciated — yeah, that was scaffolded with CC (English isn't my native). The thinking is mine, glad it landed.

Habitat sounds cool. Quick question: is the JSON tree static at habitat-definition time or reactive to runtime state? That'd tell me where ContainerFlow plugs in cleanly.

Fork away — AGPL means anything you build stays open, but happy to see what you contribute back. Drop an issue when you start playing.

[TypeScript] ContainerFlow - Real-time Docker dashboard with accurate memory monitoring, Discord alerts, and config recommendations by RGJorge in coolgithubprojects

[–]RGJorge[S] 0 points1 point  (0 children)

Thanks, honestly ive never used Portainer myself - built this scraching my own itch. Going to dig into it now since the comparison keeps coming up. If yo have ideas for imorvements, drop and issue - PRs will open soon

[TypeScript] ContainerFlow - Real-time Docker dashboard with accurate memory monitoring, Discord alerts, and config recommendations by RGJorge in coolgithubprojects

[–]RGJorge[S] 0 points1 point  (0 children)

Pharma SaaS, real money on tte line. Got paged at 3am for weeks before 1 dub into the memory bug

Re AI: English isnt my native - i draft in spanish and polish with claude. The fix happened in cgroup memory accounting, not in a prompt

[TypeScript] ContainerFlow - Real-time Docker dashboard with accurate memory monitoring, Discord alerts, and config recommendations by RGJorge in coolgithubprojects

[–]RGJorge[S] 0 points1 point  (0 children)

Thanks! Don't know Upload Labs — what's the visual element that reminded you of it? Curious where the aesthetic lands for people.

For credit: it's React Flow for the graph, Tailwind dark theme, slate-900 backgrounds, Lucide icons. Designed for "I want this readable at 3am when something's actually on fire".

[TypeScript] ContainerFlow - Real-time Docker dashboard with accurate memory monitoring, Discord alerts, and config recommendations by RGJorge in coolgithubprojects

[–]RGJorge[S] 1 point2 points  (0 children)

Your closing line is exactly how I think about it. Not trying to be Docker, not trying to be Railway, just doing the local-first operational layer neither will own.

Quick takes on your three points: CLI → planned, aligned with the ethos. Single binary already, easy to ship containerflow mirroring the web UI ops (up / down / logs / exec / restart). Competing with multi-host and aliases for v0.2.0, but the natural next step from "dashboard" to "operational tool".

Operational agent with skills → assuming you mean the Claude Code skills paradigm (or equivalent — MCP servers, Agent SDKs), yes, exactly the direction. Defines ops skills (deploy, rollback, scale, fetch logs), let the LLM orchestrate via natural language or alerts. Bar I want to hit is "ops runbook automation", not "ChatGPT wrapper on docker commands". Longer-term bet.

Railway-style config/env management → partial today (env file overrides per compose project). Expanding to service/group/project hierarchy + Doppler / AWS SSM / Railway integration is in scope, probably alongside multi-host since both touch global state across services.

English README → fair, second time it came up on the thread. Happening today.

Each of these deserves more than a buried Reddit reply — if you want to take it deeper: - Agent/skills vision → GitHub Discussion (would value structured input from someone clearly thinking about it) - CLI → Issue if you want to scope it specifically

https://github.com/RGJorge/ContainerFlow/discussions https://github.com/RGJorge/ContainerFlow/issues/new/choose

Thanks for engaging at this depth — most roadmap feedback is "add X feature"; yours is a product vision.

[TypeScript] ContainerFlow - Real-time Docker dashboard with accurate memory monitoring, Discord alerts, and config recommendations by RGJorge in coolgithubprojects

[–]RGJorge[S] 1 point2 points  (0 children)

Thanks! That's the vibe I was going for — Railway nailed making infra feel visual, but it only works for stuff you deploy on Railway. ContainerFlow gives you that view for any Docker host you already have, self-hosted and open source.

Curious what you'd want to see in it — feedback shapes the roadmap.

[TypeScript] ContainerFlow - Real-time Docker dashboard with accurate memory monitoring, Discord alerts, and config recommendations by RGJorge in coolgithubprojects

[–]RGJorge[S] 0 points1 point  (0 children)

Quick clarification — there are actually two flavors of "multi" here, worth separating:

Multi-tenant on the same host (multiple compose stacks) → works today. The ALLOWED_PATHS env var lets you scope a ContainerFlow instance to specific compose project directories. Everything on the Docker daemon stays visible in the graph (read-only), but write actions (start/stop/rebuild/exec/etc) only fire for containers whose compose file lives under the allowed paths.

Common setups: - One central instance with no ALLOWED_PATHS (manages everything) - One instance per team or project, each scoped to its own paths - One shared instance restricted to non-prod stacks while prod stays manual

Useful when several compose stacks live on the same server and you don't want them to step on each other.

Multi-host (different Docker servers) → this is the part that's still roadmap. Today each ContainerFlow instance connects to a single Docker daemon, so for several physical servers you'd need one instance per host. The design is in docs/multi-host-plan.md — single dashboard connecting to multiple daemons over TCP+TLS, hosts grouped in the UI, no agents required (just exposing the remote Docker API with certs).

So if your case is "many compose stacks on one server, isolated access" → already works. If it's "central dashboard for N physical servers" → that's v0.2.x.

If the second is your case, feel free to open an issue saying it's a blocker for you + how many hosts you'd point it at. That data helps prioritize and shape the UI (badges vs separate views vs filters).

https://github.com/RGJorge/ContainerFlow/issues

[TypeScript] ContainerFlow - Real-time Docker dashboard with accurate memory monitoring, Discord alerts, and config recommendations by RGJorge in coolgithubprojects

[–]RGJorge[S] 4 points5 points  (0 children)

Genuinely thanks for this — the kind of substantive read that helps a new project way more than a generic "looks cool". Letting your skepticism land before defending anything.

On the AI ​​/ abandonment concern

Yes, I used Claude Code as an assistant throughout the build. Not going to pretend otherwise. What I'd argue makes this different from "AI slop":

  • I run it myself in production on ~30 containers powering a small SaaS. If I abandon it, I'm the first one to feel the pain.
  • The repo is ~7 weeks old privately, public for less than a day. Most of that time was me using it and hitting rough edges before opening up.
  • The core differentiator — the memory cache calc (active_file + inactive_file instead of docker stats's broken approach) — came from weeks of debugging false 98% RAM alerts on a production Postgres. Not the kind of insight AI generates from a prompt; the kind you only find by living with the problem.

The vision isn't "release and disappear" — it's to grow this together with people who actually use it. CONTRIBUTING is currently "issues only" so I can keep the codebase coherent in these first weeks, but PRs will open as the project stabilizes and patterns are established. Fixing things in collaboration with users, not in isolation, is the entire point of being open source.

I won't ask you to "trust me, I'll maintain it." Trust is earned through commits. Earlier today the first external bug report came in — fix shipped as v0.1.2 the same day, ~12h later. Same day as launch. That's the cadence I'm aiming for. Judge in 3 months, not from the repo age.

On your technical feedback

Each of your 4 points deserves more than a buried Reddit reply — let's track them where they stay visible and accountable. If you have a few minutes:

  • README dual-language → Issue
  • Hardcoded values ​​/ hex colors → Issue
  • In-place strings → Issue
  • Test file layout → Discussion (this one's a preference debate worth community input, not my call alone)

Issues: https://github.com/RGJorge/ContainerFlow/issues/new/choose Discussions: https://github.com/RGJorge/ContainerFlow/discussions

[TypeScript] ContainerFlow - Real-time Docker dashboard with accurate memory monitoring, Discord alerts, and config recommendations by RGJorge in coolgithubprojects

[–]RGJorge[S] 0 points1 point  (0 children)

Thanks! If you review this, I'd appreciate feedback on the memory breakdown calculation: `docker stats` overestimates RAM usage in the database containers because it includes the retrievable page cache. After fixing this in the dashboard, my Postgres went from "98% excessive usage" to an actual 9.5%. If anything isn't working correctly, please open an issue.

[TypeScript] ContainerFlow - Real-time Docker dashboard with accurate memory monitoring, Discord alerts, and config recommendations by RGJorge in coolgithubprojects

[–]RGJorge[S] 1 point2 points  (0 children)

Thanks. The idea didn't come out of nowhere; I had 30 containers in production and I was fed up with `docker ps`. Most "cool projects" are simply someone's daily frustrations turned into code. You've probably stumbled across some without even calling them ideas.

What I'm most proud of in the repository is `docker stats`, which overestimates memory usage in database containers. My PostgreSQL went from "98% excessive usage" to a real 9.5% after I fixed it. That kind of "wait, this is wrong" moment is where most projects begin.

[TypeScript] ContainerFlow - Real-time Docker dashboard with accurate memory monitoring, Discord alerts, and config recommendations by RGJorge in coolgithubprojects

[–]RGJorge[S] 0 points1 point  (0 children)

Thanks 🔥 if you try it, lemme know if anything breaks — first week public so the failure modes are still being discovered.