CLI Purity vs. GUI Convenience: The Server Admin Battle Between SSH Experts and Web Dashboard Lovers
The community centers on selecting the optimal toolset—ranging from Web UIs like Cockpit and Portainer to raw CLI/SSH—to manage self-hosted services, while hardware choice involves everything from NUCs to Raspberry Pi units.
A sharp split defines the management approach. Some experts, citing minimal overhead and security, champion the CLI/SSH workflow. Conversely, others, like 'dudesss', demand web interfaces for simple tasks like backups and restarts, explicitly avoiding full shell access. Contributors like 'poVoq' point to Cockpit's utility, while others favor dedicated container tools like Dockhand for specific, limited interaction.
The consensus favors powerful, mixed environments: running virtualization stacks like Proxmox on solid hardware while utilizing container orchestrators. The primary fault line remains between the 'it must be command line' camp and the 'I need a dashboard view' camp, with 'Dave' suggesting hardware separation for critical resilience.
Key Points
CLI/SSH methods offer superior security and minimal overhead for administration.
Strongly argued by 'sk' and 'GreenKnight23' as the most fundamentally sound approach.
Web GUIs are preferred for glanceable, non-destructive management actions.
Highlighted by 'dudesss', who needs buttons for Backup/Restore but nothing more.
Dedicated hardware isolation enhances resilience across multiple services.
'llamatron' suggested using separate, dedicated systems for components like Pi-hole alongside the main Proxmox cluster.
Portainer and other container management GUIs are highly utilized for orchestration.
This toolset is mentioned repeatedly for managing container lifecycles.
Cockpit is touted as a strong, general-purpose web administrative interface.
'poVoq' suggested it, noting its useful integration with Podman.
Using a Raspberry Pi for single, non-critical tasks is a sound strategy.
'Dave' suggested this model for services like Pi-hole to maintain main server isolation.
Source Discussions (3)
This report was synthesized from the following Lemmy discussions, ranked by community score.