Hey fellas, I noticed a lot of people will install/boot headless versions of this software on raspi to conserve resources. If I go through installing what I need to install via the GUI/Terminal, will I have any issues when I’m finished turning on the boot to CLI? I assume this won’t affect the background process too much (unless of course something I install needs a GUI.)

Along with that, will I still be conserving the same amount of resources as if I ran headless to begin with. Running x64 Bookworm on raspi 4 (8gb) if that matters, and have a general self-hosting setup.

Thanks in advance!

  • @[email protected]
    4•1 year ago

    If you disable graphical.target, no processes related to GUI will launch and consume any resources other than disk space.

    • chingaderaOP
      1•1 year ago

      Awesome, I’ll look into this. Thanks!

    • chingaderaOP
      1•1 year ago

      I appreciate it, I was more so wondering whether or not I could keep my existing build as is aside from the GUI. I’ve done it the headless/CLI via ssh route previously but thought I’d check out using the GUI during the setup stages and being able to enable/disable the GUI at will and how that would affect performance vs installing only CLI at the start of the build.