131–140 of 188 posts
Question from a Cockpit PO: if you were to choose one feature to add to the project what that feature would be?
the opinion you didn't ask for: avoid admin UIs... at best they make you lazy, at worst a security nightmare
Earlier quoted context omitted.
Going for a shameless plug - I am working on an observability dashboard for Docker Swarm: https://github.com/Radiergummi/cetacean Also works for a single node cluster. Maybe that’s closer to what you’re looking for.
Hey that’s pretty cool, nice to see someone paying attention to Docker Swarm (it’s nice for simple deployments, like multi-server Compose). You might want to add some screenshots to the docs though. There was also Swarmpit but it didn’t really get that much love, sadly: https://github.com/swarmpit/swarmpit/issues/719 Portainer is pretty nice feature wise but even with lowered MTU I still get odd networking related is…
I love swarm! If only it wasn’t the unloved step child…
If you have a git repo for anything that's supposed to be an interface to anything, please put one screenshot at the top of your readme. I get that the website has these, but its the best way to let me know more about your product in one shot.
Earlier quoted context omitted.
Which is fine and all but repos with such sparse README's are not doing themselves any favors.
Including images in a readme means committing (maybe large) binary files to the repo.
I installed the latest Fedora Server on my Framework Desktop and noticed that Cockpit was enabled automatically. Overall impression is that its pretty good for getting a quick overview of things and you can certainly do _some_ administration with it, but you run into its limitations pretty fast trying to get any serious work done with it. It's probably great for those who are new to Linux and want that NAS-like admin…
Earlier quoted context omitted.
One of my favorite interview questions: "Here are some SSH credentials. What does this system do?" Sometimes there aren't any docs. Sometimes the docs are wrong. It's important to be able to establish what the actual running situation is.
When I was interviewing people on behalf of a client, I was surprised at the number of people who didn't even know what SSH was. This was for a mid-level software developer and not a junior and they all came with glowing resumes. They all insisted that it was essential to have a CI/CD process but didn't even know what the "CD" part even did. Apparently you just "git push" and the code magically gets on the server. Th…