I am trying to use my old laptops for self-hosting. One has a 6th gen Intel Core i3 (4GB ram), the other has an 11th gen Intel Core i5 (8GB ram). I have previously tried both ubuntu server and desktop but couldn’t get it to work well. For the former I found it difficult to remote ssh and the latter I had difficulty installing Docker containers. (I’m not very good with the command line)

I would like to find an OS that is easier to setup with less of a neccesity for the command line (I would still like to learn how to use it though, I don’t want to get rid of it entirely!). I’ve heard of CasaOS, is that a good option? It seems quite easy to use. What about other alternatives?

    • drspod@lemmy.ml
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      1
      ·
      2 months ago

      Does Unraid still use JBOD with a single parity disk or have they moved to a sane drive layout?

  • pHr34kY@lemmy.world
    link
    fedilink
    English
    arrow-up
    9
    ·
    2 months ago

    Almost all of selfhosting is editing config files, setting permissions and starting/stopping services.

    Setting it up so you can administer a server by desktop is probably as hard as learning how to edit config files from a terminal. Maybe harder.

    • TMP_NKcYUEoM7kXg4qYe@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 months ago

      Yep my thoughts. New selfhosters think the hard part of selfhosting is command line but that’s “kinda” like thinking that the hard part of math is writing numbers on paper. Terminal is just the medium, not the complex part. Navigating filesystem and editing files is easier on the desktop but changing permissions and managing services would be be extremely difficult for a newbie without using the terminal because (almost) every online tutorial uses terminal. OP would have to learn how to translate the terminal command to its desktop counterpart at which point they might as well use the terminal.

      OP also has an XY problem. They asked for a system which does not require terminal usage but they should have actually asked for an easy to set up system. People are recommending things like Yunohost though, so it’s fine in the end.

      • Lka1988@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        2
        ·
        2 months ago

        OP also has an XY problem.

        Oh god, that… I recently realized that I’ve been fighting that concept with one of my cars for over a year now. Just this week, I finally figured out the right troubleshooting path 😂

  • Encrypt-Keeper@lemmy.world
    link
    fedilink
    English
    arrow-up
    6
    ·
    edit-2
    2 months ago

    I believe all of these are actually just running Debian as the actual OS underneath, but they give you a webui that makes deploying apps easier.

    Of these three, I like the look of Cosmos the most. Seems to be security focused and comes with a reverse proxy and a built in SSO solutions. That’s something that’s usually a pain in the ass to set up yourself.

    There’s technically that stupid ass LTT OS but I’m purposely leaving that one out.

  • q7mJI7tk1@lemmy.world
    link
    fedilink
    English
    arrow-up
    6
    ·
    edit-2
    2 months ago

    For what it’s worth given the age of this thread and disagreement going on in it, I would recommend Unraid.

    Easy for a beginner, with enough to take you up to intermediate level: a web GUI for pretty much all the required terminal commands. It’s been around for years, is not going away, but instead getting updated. Works on any old eBay hardware and most of all, the community there are very supportive of beginners. There’s also lots of YouTube tutorials.

    It ticks all the boxes for easy self hosting. It’s just not for Linux protocol purists.

    EDIT: I’m learning a lot from this thread, and it’s interesting to see how tolerant people are for self hosting. I would add in my vote for Unraid: it allows me to be dynamic with the time I have for self hosting. I’m sometimes extremely busy and don’t have the time to keep my self hosting updated, so the web GUI is essential for basic maintenance. Then there are times when I do want to waste an afternoon trying something in terminal and learning more, and that’s when Unraid again comes to the rescue. I couldn’t self host with 100% terminal, and neither would I want to with 100% GUI. The best self hosting platform is one that can mix them up efficiently and effectively. I am keen to try some others mentioned here, as some look quite interesting. However NAS is a massive element of what I need for my homelab, so Unraid will stay for now.

  • Appoxo@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    5
    ·
    edit-2
    2 months ago

    I am very much a Windows user and my journey went like this:
    Raspberry Pi with OMV -> SSH on OMV -> Mostly Terminal on OMV -> Docker + Portainer to deploy containers -> Transition to docker-compose -> Setup my own VM with Debian completely in the CLI (excluding the first setup of the VM)

    I use Linux (primarily Debian because of Raspberry as I don’t like what I hear about Ubuntu) primarily for VMs and servers and Windows as the client OS

    • Lka1988@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      3
      ·
      2 months ago

      I love the command line. A terminal window is always open on whatever computer I’m using at the moment, even when I was running Windows.

      But I also like having a dashboard to see what’s going on, all right in front of me. I have ADHD, and if I can’t see it, then I will forget it exists. I use command line to handle more granular tasks, and have various UIs to help me handle other things, like Proxmox (obvious), Dockge (docker stacks), OMV (NAS), Cockpit (all of my computers have this, really good for remote control), and a few other things I’m forgetting.

  • whotookkarl@lemmy.world
    link
    fedilink
    English
    arrow-up
    5
    ·
    2 months ago

    The command line is an exceptionally useful tool, you may want to spend a little time getting familiar with it and common command line tools that would probably make self hosting almost anything easier.

    It’s like wanting to learn to play guitar but not learning how to restring and tune it, sure it’s not necessary but you’re going to be overly dependent on others to do something you could learn for yourself with a little time and patience, and it will probably broaden your perspective on what you can do once you do get familiar with how to pipe commands together and combine basic tools into something more sophisticated and complex.

  • glitching@lemmy.ml
    link
    fedilink
    English
    arrow-up
    5
    ·
    2 months ago

    don’t go with server variants of the OS. they are intended for boxes that work without display and keyboard, which you have. instead, install any normal distro you’re familiar with. it’s infinitely easier to fix something with the full GUI at your disposal.

    this is just your first install, you will iterate, and through that process you’ll get better and leaner, in terms of underlying OS. think of it as training wheels on a bike, you’ll pull them off eventually.

    wired connection only, leave wireless turned off, and assign it a static IP address.

    don’t do containerS, do one container first. figure out where you’re gonna store the compose files, where it will store data, how you will back that data up, etc. then add another. does it fit into your setup? do you need to modify something? rinse. repeat.

    casaOS, aside from it’s murky background (some chinese startup or sumsuch, forgot?) doesn’t provide that path forward nor allows you to learn something, too much hand holding.

    good luck.

  • N0x0n@lemmy.ml
    link
    fedilink
    English
    arrow-up
    3
    ·
    2 months ago

    Hey :) I’m not giving you any recommendations but want to give you my personal experience !

    5 years ago I had absolutely no clue about Linux/CLI/networking/docker… You name it ! And I also wanted to repurposed and old laptop as a server.

    The first distro I installed on my server was Debian ! Why? Because I remembered my brother said something along the line: “Every server infrastructure is run by Debian or a Debian derivative”. So this sounded like the perfect thing to install as a server distro :) !

    5 years later I’m still running Debian on this old laptop and it’s going strong ! Never did it failed me except if I did something wrong over the CLI !

    As you guessed it, you will need some degree of proficiency on the command line specially if you install your distro without a graphical user interface, which I would recommend… Yes, the CLI isn’t easy to beginning with and you will do some mistakes that will need a full reinstall of your system… But before you learn to move, you learn to stay up right on your legs and this involves a lot a failing !!

    It’s not mandatory, you can install a lightweight GUI and take your time. There are a lot of application with good UI which will help you out ! However, not once did I regret to take the harder route and learned so many things along the way ! After this amount of time in the CLI, I can say I’m getting quite good In navigating my system, keeping it healthy and alive :p !

    Okay, If it’s a matter of time I get it ! We only have 24h a day and most of this time is already spend at work/school, family time, friends, sleep, eat ! If you’re lucky enough to have 2 hours to spare to tinker arround, a UI is a good idea to keep a healthy balance between all your personal activities ! But keep in mind, both are thorny and have their fair share of issues and debug time.

    Last words, have fun with your system :)

  • couch1potato@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    3
    ·
    2 months ago

    I was in the same spot about 3 years ago and I started with Unraid. Got me into docker and dipping my toes into command line stuff.

    Honestly though you’re going to quickly outgrow your old laptops…

  • testman@lemmy.ml
    link
    fedilink
    English
    arrow-up
    3
    ·
    2 months ago

    YUNOHost iso is basically just Debian, but the one-click-install for various self-hosted things is it’s primary purpose. All done through web interface.

  • irmadlad@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    2 months ago

    (I’m not very good with the command line)

    Me either so I take a lot of notes about commands and command sequences. Also, I find that Grok is pretty decent at explaining commands. AI is a wonderful tool, but you also need to do your due diligence in ascertaining whether AI has given you the correct information. I would not copy/paste random commands into a production server, but rather I have a small test server for that kind of stuff. Once I have the command, tested, and understand the command, I can then use that in a production environment.

    In as much as I love a good WUI, you will have to learn some cli, it’s just inevitable, especially in a headless environment. It may seem daunting at first because there are literally thousands of commands and command sequences. I honestly doubt if even the geekiest nerds on the planet know all by heart. For each command sequence, there are probably hundreds of ways to compose the same command. I would admonish you to download Notepad ++ and start keeping notes on the commands you use. Later on, the fun part is looking back on your notes to see all the commands you now know and what they do.

    Core utilities (like ls, cd, cat, etc.) from projects like GNU Coreutils provide around 100-200 commands. Additional tools from packages (e.g., grep, awk, sed) and system utilities (e.g., systemctl, iptables) can add hundreds more. On a system with many packages installed, running compgen -c | sort -u | wc -l in a Bash shell might show 2,000–10,000+ unique commands, depending on the setup.