Comment on Do folks managing servers mainly do so via command-line interfaces?

knobbysideup@lemm.ee ⁨1⁩ ⁨year⁩ ago

• richieadler@lemmy.myserv.one ⁨1⁩ ⁨year⁩ ago

  You can’t really do configuration management with a GUI.

  Cries in Windows Server

  source
• ALostInquirer@lemm.ee ⁨1⁩ ⁨year⁩ ago

  How much effort is ‘run command with parameter’ documentation […]

  Tbh it’s less so the effort and moreso, how understandable is the documentation? A good GUI has the benefit of visual design explaining without words what may take a lot of documentation that may or may not be easily understood depending on the writer, which in many technical situations is someone deep in the jargon that has forgotten the way back to more accessible language.

  Once you’re familiar with the commands, no doubt as many others have said it’s more efficient (especially once you’re knowledgeable enough to write scripts for frequent sets of commands), but there is a learning curve at play as one muddles through documentation in a similar way to an unfamiliar GUI.

  source

  • Nibodhika@lemmy.world ⁨1⁩ ⁨year⁩ ago

    If you understand that the terminal is better in the long run then you answered your own question, most people who fiddle with servers do so for a long time so the time investment is worth it. A similar analogy is learning knife skills, if you just cook for yourself being able to chop an onion in seconds saves you a minute a day from the one onion you used, not really worth outside being a neat party trick. But if you work in a kitchen that’s mandatory, chopping an onion in seconds means you save an hour for the 60 onions you chop in preparation for the service. Same idea for GUIs/terminal, it has a higher learning curve but if you try to avoid the curve you’ll never be able to do it fast, so the time investment is worth it if you’re going to be doing this daily (like most server admins do)

    source

    • ALostInquirer@lemm.ee ⁨1⁩ ⁨year⁩ ago

      Same idea for GUIs/terminal, it has a higher learning curve but if you try to avoid the curve you’ll never be able to do it fast, so the time investment is worth it if you’re going to be doing this daily (like most server admins do)

      Yeah, part of the thinking behind this question was with those doing this more as a hobby in mind (e.g. self-hosters) where it’s sort of a limbo. You may be doing it daily as part of your hobby, but also never on the level that really demands the degree of proficiency or efficiency you describe as you’re not going to be handling a large network of servers (probably), so on one hand learning the CLI may simply be part of the fun, but on the other, it may also lean into overkill depending on what you’re aiming to do.

      source

      • Nibodhika@lemmy.world ⁨1⁩ ⁨year⁩ ago

        I think it’s still worth learning it as a hobbitst, same thing as the knife skills for someone who likes to cook, you don’t need to be super proficient with a knife, but the basics of knife skills will up your cooking by a lot, at some point you’ll reach diminishing returns and you’ll stop learning, but the basic is almost essential. Same thing for CLI, you don’t need to become a master in the command line, but being comfortable around it will help you a lot. In other words, trying to run a server without CLI is like trying to cook without a knife, is it possible? Depending on what you’re trying to do yes but in general you’re shooting yourself in the foot, just because a blender can replace a knife in some instances doesn’t mean you can use it for all of the same things you would use a knife, a GUI is the blender of servers, it makes some things easier but is not as versatile.

        source
  • gornius@lemmy.world ⁨1⁩ ⁨year⁩ ago

    No, any documentation >>> GUI. GUI relies on your previous experience with similar environments. Just jump into a GUI of Visual Studio (not code) project configuration and see for yourself.

    source