Yeah, okay, that makes a lot of sense. I asked in another comment as well. I read about “headless” servers, which from what I understood means no GUI. Would you recommend that, or use a GUI first and then move to headless when the actual server is in place?
Comment on "Ultimate" guide for literal beginners
slazer2au@lemmy.world 3 days agoDebian is good to start with as one of its key tenants is stability. Which is what you want in any environment.
A lot of popular distros like Ubuntu and Mint are based on it.
Yesbutnotreally@lemmy.world 3 days ago
Zos_Kia@jlai.lu 3 days ago
I feel GUIs complicate everything. You need graphics drivers and a display server and a compositor and a window manager etc… it’s a pain and in the end you still have to open a console to type in commands for your actual self hosting. Not worth the effort in my opinion, and it’s better to bite the bullet and get used to the terminal and ssh early.
I recommend using something like tmux or screen, so you still have basic comforts like tabs and multi task. Once you get used to it you can configure it and add themes and plugins if you like. A modern tmux setup really feels like a desktop except everything is faster and it barely consumes any resources.
poweruser@lemmy.sdf.org 3 days ago
I second the Debian recommendation, with one caveat: if ever you need to install software that is not maintained by Debian (I.e. it is installed using a command like
make installinstead ofapt install) then you could run into significant problems.Debian uses a system (called APT) to manage the logistics of all your apps and libraries. This is wonderful until you add a program using a different method that APT doesn’t know about. In that case you can “end up in dependency hell” where your system can no longer update or install new packages.
Advanced users can work around this limitation to install things safely, but for a user just starting out I suggest to only ever install packages that exist in the Debian repositories (that is, can be installed with APT or one of its various frontends). This can mean the programs are a little outdated or not available.
Debian has a document that explains this in greater detail, which I suggest every Debian user reads: Don’t Break Debian
I started with Mint, then dipped into KDE Neon and Kubuntu, and these days I rock Debian on my server because I want absolutely nothing to fall over if possible. And that’s how it’s been for me. I SSH into it every couple of weeks to run updates, and that’s about it.
Debian is great. Boring, and great.