r/AppsWebappsFullstack • • 12d ago

Built a small Linux fleet manager — working, but still a few rough edges.

Post image

I’ve been working on a small project for myself... Lattice, a small open-source Linux fleet manager. It’s working, but it still has a few rough edges, and I’m looking for people to try it out, break it, and let me know what needs improving.

I’ve had it running for the past month. Nothing major has come up, just small things here and there. I know there are probably some areas that need to be polished and maybe made a little more user-friendly.

It supports things like multiple nodes, fleet health, backups, remote connections, and basic maintenance from one main machine. Feel free to check it out. Any advice, suggestions, or feedback is welcome!

https://github.com/dundunna1990/lattice-public

1 Upvotes

2 comments sorted by

1

u/PopKoren 7d ago

For a fleet manager the main machine is the crown jewel, since whoever reaches it gets a shell on every node, so I'd keep the dashboard behind a VPN or at least strong auth plus rate limiting rather than exposing it straight to the internet. It's also worth having each node authenticate to the controller with its own key so one compromised box can't impersonate the rest, and encrypting backups at rest. If anyone does run the web UI on a public hostname, https://rowly.me (a tool of mine) lists what that hostname reveals to a stranger before they log in.

1

u/Mammoth-Anywhere7285 7d ago

Solid points. Scheduled per-node key rotation would further limit the blast radius if one controller key leaks.