|
|
|
|
|
by c0balt
312 days ago
|
|
The GUI looks useful but for the core problem: > Managing multiple Linux servers usually means juggling terminal windows and copy-pasting snippets/scripts. [...] There is already a plethora of tooling for many of these points. Not a lot of GUI stuff but ansible seems to cover a lot of ground (inventory, organized playbooks instead of shell scripts). Ansible also "just" uses SSH as a transplrt mechanism. This feels like a solution that tries to support a flawed workflow instead a solution improving the workflow itself. |
|
When I need to accomplish something relatively large and standard(e.g. two node MySQL installation with a replica), I'd reach for my Ansible playbooks.
However, there are certain one-off flows for which I think SB has a sweet spot. Let's say I'm an agency managing web apps for multiple clients with separate VPS(es)/bare metal servers for each client.
If I get a ticket saying something's wrong with one of their app or its dependencies(let's say MySQL), it would be very easy for me to check the container health in the Docker tab and then check the detailed logs in the Logs tab to identify the issue. During this investigation, I might also check the Ports and other tabs to check external connectivity.
Another quick one off flow I can think of is to quickly check if everything's working after running an Anisble playbook on my server(s).
It might be worth writing Ansible playbooks for these workflows if one keeps finds they're doing them over and over, but I feel that a GUI option has some merit as well.