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?

  • @hperrin@lemmy.ca
    link
    fedilink
    English
    78
    edit-2
    2 months ago

    If you’re afraid of the terminal, you won’t get far in self hosting. You should learn to use the terminal. It’s not as scary as people make it sound.

    You mentioned having issues with SSH into your old server. You can install a desktop environment if it makes things easier for you, but you should still learn how to be proficient in the terminal. Proxmox might help. It lets you create and manage VMs through a web interface. It can be annoying if you’re not super familiar with networking though.

        • @masterspace@lemmy.ca
          link
          fedilink
          English
          -23
          edit-2
          2 months ago

          Notice that it hasn’t amongst mainstream consumers.

          You know what self hosted projects have been successes? Plex and Home Assistant. You know what projects don’t require the terminal? Plex and Home Assistant.

          • @atzanteol@sh.itjust.works
            link
            fedilink
            English
            8
            edit-2
            2 months ago

            Notice that it hasn’t amongst mainstream consumers.

            Good. Mainstream consumers don’t understand enough about networking and computer security to be trusted to self-host anything beyond desktop applications. And even that is debatable. They’re so bad at it that walled-gardens have become ubiquitous just to keep viruses from running rampant.

          • @tauren@lemm.ee
            link
            fedilink
            English
            6
            edit-2
            2 months ago

            Notice that it hasn’t amongst mainstream consumers.

            What? A niche technical hobby isn’t popular among mainstream consumers? Wow!

            Mainstream consumers don’t know words “Plex” and “Home Assistant” either. There are already products that target these people. And there are products targeted at technical people. We need diversity.

            • @masterspace@lemmy.ca
              link
              fedilink
              English
              -122 months ago

              Self hosting is just an extension of open source software. It’s only goal is being able to run your own backends of apps to not be exploited by major companies. It’s goal is not to be a niche technical hobby, if that’s your goal in its own right, then get a model train or a Warhammer set.

              Mainstream consumers don’t know words “Plex” and “Home Assistant” either.

              Yes, they do lol. It’s flat out weird to think that the only people who have ever heard of pirating are software developers and server admins who use the command line.

      • baduhai
        link
        fedilink
        English
        102 months ago

        It isn’t, self hosting just isn’t for everyone, and it never will be.

      • @aMockTie@lemmy.world
        link
        fedilink
        English
        8
        edit-2
        2 months ago

        Imagine if OP asked: “I want to repair/maintain my own car, but I don’t want to open the hood or get under the car. What are my options?”

        Obviously there would be some options, but those options would be very limited and not ideal. This is very similar. Self-hosting, like self-repair of a vehicle, requires some foundational knowledge and understanding of your specific hardware, usecase, and needs, as well as the knowledge and ability to bring those things to fruition. There is no single universal answer that applies to everyone, but those skills can be acquired by anyone.

        I don’t think self-hosting is any more doomed than self-repair of a vehicle. It’s certainly not for everyone, but it can be satisfying, rewarding, enjoyable, and generally optimized for those who choose to participate.

      • @gravitas_deficiency@sh.itjust.works
        link
        fedilink
        English
        7
        edit-2
        2 months ago

        Self hosting isn’t likely to ever get to the point of “plug and play”. It’s inherently incredibly flexible and different people will do different things with it. Some people just want NAS. Some people want to build a router. Some people want to have a modest compute farm that they physically own. Some people want a virtualization playground. Or pretty much anything else you can think of, or some combination thereof.

        For instance, I custom built a 2-tier + optane cached NAS running proxmox, and I have a handful of old thin clients I can spin up for doing Beowulf things when I feel like it, and I also have another repurposed thin client with an old enterprise-grade SFP+ NIC running pfSense as my router that can support up to 10g (futureproofing).

      • @hperrin@lemmy.ca
        link
        fedilink
        English
        52 months ago

        No. You really don’t want to self host unless you are pretty familiar with how these services work. Otherwise, you’re just setting yourself up to get hacked.

        • @masterspace@lemmy.ca
          link
          fedilink
          English
          -5
          edit-2
          2 months ago

          I mean what’s the point of “self” hosting then?

          If you have to be a professional server administrator to host one of these services, then why even have a self hosting community as opposed to just a hosting community for server admins to discuss how to set and configure various services? Is this community dedicated to just discussing the uniqueness of managing a home server without a static IP?

          • @hperrin@lemmy.ca
            link
            fedilink
            English
            92 months ago

            If you want to ride a bike, you need to learn to balance on a bike. That will never change. You don’t need to be a professional cyclist.

            If you want to self host, you need to learn some basic administration, and that includes the terminal. That will never change. You don’t need to be a professional server administrator.

            You might be able to get by with some hand holdy solution that offers a few things you can do, but just like riding a scooter is much more limited than riding a bike, using a turnkey solution is much more limited than setting up your own server.

            Imagine wanting to self host but refusing to learn how to forward a port. There are just some things you need to learn. Like I said in my original comment, the terminal is not as scary as people make it sound. Right now, you are the person making it sound scary.

    • @dmention7@lemm.ee
      link
      fedilink
      English
      72 months ago

      Beginner here (to Linux and networking anyways), running Unraid for about 18 months now. Fully agree, it’s been great for actually getting up and doing useful things quickly and relatively pain free.

      Eventually I would like to try working backwards and getting things running on a more “traditional” server environment, but Unraid has been a great learning tool for me personally.

      It’s like… Maybe some folks learned to overhaul an engine before they got their driver’s license, but lots of people just need to a car to get to work and back today, and they can learn to change their oil and do a brake job when the time comes.

    • @drspod@lemmy.ml
      link
      fedilink
      English
      12 months ago

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

      • @charles@lemmy.ca
        link
        fedilink
        English
        32 months ago

        Other than ZFS as someone mentioned already, they also offer dual drive parity now. IMO it’s a good balance to also allow a very flexible and easily expandable array.

  • @pHr34kY@lemmy.world
    link
    fedilink
    English
    142 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
      42 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
        link
        fedilink
        English
        32 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 😂

  • Günther Unlustig 🍄
    link
    fedilink
    English
    9
    edit-2
    2 months ago

    I can recommend you Debian, since it’s the “default” for many servers and has a lot of documentation and an extremely big userbase.

    For web interfaces, I can recommend you, as you already mentioned, CasaOS and Cockpit.

    I used CasaOS in the beginning and liked it, but nowadays, I mostly use Cockpit, where I have the feeling that it integrates the host system more, and allows me to do most of my maintenance (updating, etc.) quite easily.

    CasaOS is more aesthetic imo, and allows you to install docker containers graphically, which is better for beginners.
    I personally do my docker stuff mostly via CLI (docker compose file) nowadays, because I find it more straightforward, but the configuration CasaOS offers is easier to understand and has nice defaults

    • sbird [moved to sopuli]OP
      link
      fedilink
      English
      22 months ago

      Thanks, that was really helpful :D

      I’ll try CasaOS then, and later maybe I could move to Debian once I get better at the command line!

  • @q7mJI7tk1@lemmy.world
    link
    fedilink
    English
    9
    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.

  • @glitching@lemmy.ml
    link
    fedilink
    English
    82 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.

  • @whotookkarl@lemmy.world
    link
    fedilink
    English
    82 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.

  • sbird [moved to sopuli]OP
    link
    fedilink
    English
    62 months ago

    I ended up installing Debian since Yunohost can’t install and my old laptop doesn’t meet the hardware requirements of TrueNAS Scale

  • Encrypt-Keeper
    link
    fedilink
    English
    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.

    • sbird [moved to sopuli]OP
      link
      fedilink
      English
      12 months ago

      Cosmos does look quite good. TrueNAS can’t run on my old laptops so HexOS was never really an option

  • @Appoxo@lemmy.dbzer0.com
    link
    fedilink
    English
    6
    edit-2
    1 month 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
      link
      fedilink
      English
      32 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.

  • @anamethatisnt@sopuli.xyz
    link
    fedilink
    English
    62 months ago

    I would recommend trying out Cockpit (Github) and Portainer (Github).
    Cockpit gives you a WebUI for Linux and Portainer gives you a WebUI for Docker.
    Personally I usually run Debian Stable for servers, but choice of distro matters little if you run stuff as Docker containers.

  • mhz (lemm.ee)
    link
    fedilink
    English
    52 months ago

    Maybe you might find home in one of those NAS ootimized distros like Openmediavault, truenas, unraid. If not CasaOS or old good Debian with portainer.

    • Lka1988
      link
      fedilink
      English
      12 months ago

      I’m all for command line, but I’m the kind of person who needs a dashboard, otherwise I forget everything. OMV has a solid dashboard and has been really good for me.

  • @WQMan@lemm.ee
    link
    fedilink
    English
    5
    edit-2
    2 months ago

    I personally use Debian. For your case, you can install lightweight desktop environments such as XFCE.

    Honestly from my point of view after reading your post, you don’t have a terminal or operating system issue, it feels like you are new to self-hosting and don’t know how to start configuring from scratch.

    Ideally you want to look for documentations or keep asking for online help. For example, with installing docker, you would want to refer to this: https://docs.docker.com/engine/install/. Welcome to system admin life, where you spend more time reading/understanding than configuring.

    Personally, you can even use AI Chatbot to help you with stuff, just be specific on the system you are on, the goal you are trying to achieve and the problem you are tring to solve.


    Which brings me to answer your next point about CasaOS: It exists so that you can skip most of the ‘system admin life’ step. It skips almost all the setup you would have needed to do on a fresh machine, and just leaves configurations. The downside is usually it eats up more resources than a self-configured install since it comes with redundant features you are unlikely to use.

    TLDR; Pre-configured OS such as CasaOS is a solid choice if you just want to set it up and be done with it. If you are here to really learn about system admin stuff, then pick any of the Linux Operating system (Debian-derivatives recommended) with a lightweight DE.

    Happy self hosting :v

    • sbird [moved to sopuli]OP
      link
      fedilink
      English
      42 months ago

      Okay, so CasaOS is easier to set up (but uses more resources and I won’t learn sysadmin stuff) whereas using something like Debian is a bit harder to set up (but uses less resources and learn more!).

      Think I might try CasaOS on my 11th gen laptop and plain Debian on my 6th gen laptop and see which I prefer

  • @Churbleyimyam@lemm.ee
    link
    fedilink
    English
    4
    edit-2
    2 months ago

    YUNOhost is designed for this. You can do almost everything graphically via the webadmin. Mine has been running for a couple of years and I’m very happy with it. I have email, XMPP (both of which were installed out of the box), a website, file sharing and a few other things. There are a tonne of apps available, including Fediverse instances, Nextcloud. It’s a very cool thing to have available for making self-hosting more accessible.

    • irmadlad
      link
      fedilink
      English
      12 months ago

      YUNOhost

      Early on sometime, I deployed Yunohost. At the time there were apps, but the catalog was sparse. I happened upon it again in a search for something else about a week or so ago. Wow! The devs have been really developing it at a cyclical rate. I was impressed. For someone just starting out and trying to get their toes wet, I could see Yunohost being a good starting point.