this post was submitted on 28 Apr 2025
81 points (87.9% liked)

Selfhosted

46410 readers
1014 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

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?

top 50 comments
sorted by: hot top controversial new old
[–] whotookkarl@lemmy.world 6 points 6 hours 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.

[–] orosus@lemmy.world 1 points 6 hours ago
[–] toynbee@lemmy.world 5 points 9 hours ago

I misread that as "self-loathing" and the answer was obvious.

[–] Ulrich@feddit.org 1 points 6 hours ago
[–] Appoxo@lemmy.dbzer0.com 6 points 17 hours ago (1 children)

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. I don't lile what I hear about Ubuntu) usually for VMs/servers and Windows as the client OS

[–] lka1988@lemmy.dbzer0.com 3 points 7 hours 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.

[–] dave@lemmy.wtf 2 points 15 hours ago* (last edited 15 hours ago)

i tried CasaOS for a quick minute. its decent and just has the basics like setting up any disks and then has an app store. its really just a front end for docker and you can manually input the details of any docker containers that arent in the store

ive mostly been running docker stuff on my Synology nas. cant think of the model number now, 218+ i think, but any of the "plus" models will let you run docker. its very similar to Casa, no messing around with command line stuff. ive been self hosting for 10 years now and never touched the command line so i dont know what people are on about here saying you will have trouble

dietpi is another thing ive used on a few devices, mainly small SBCs and raspberry pi's, but i think they might have a version that you can install on anything. its basically just debian, and it has a sort of a wizard that helps set up various things like set up disks and install apps. its headless though so no GUI unless you install one, and the wizard is run from the terminal but youre not having to type any commands at least

[–] banshee@lemmy.world -1 points 10 hours ago (1 children)

The learning curve might be a little high in some regards, but you may want to try NixOS. There are quite a few services ready to enable and customize for self-hosting, and the design makes updating packages fairly simple.

To be clear, NixOS is not a "simple" solution, but it does work well for self hosting.

[–] lepinkainen@lemmy.world 7 points 9 hours ago (2 children)

NixOS doesn’t have a curve, it’s a fucking wall 😆

[–] zenforyen@feddit.org 2 points 6 hours ago (1 children)

How is that useful to OP who asked for something "without terminals"? Unless that was a joke.

Because I've been using Arch Linux for 15 years and live in the terminal, but even though I like the idea of NixOS, it's not only scary because it is alien and I have neither motivation nor enough free time to learn a parallel world and gain non-transferable skills for a niche solution. And that with being interested in what NixOS is doing.

I would say it is horrible advice to a novice, unless you want to scare people away from learning terminals and configs and managing an operating system without GUI tools.

[–] banshee@lemmy.world 1 points 1 hour ago

I'm not interested in arguing. You're welcome to your opinion as well.

Multiple individuals noted the value of diving into non-GUI server administration, and I wanted to share a tool that could be of interest down the road.

[–] banshee@lemmy.world 0 points 9 hours ago

😄 Sometimes it's hard to remember the differential

[–] AustralianSimon@lemmy.world 4 points 18 hours ago

Mint or Ubuntu is like Windows but better.

[–] VeganCheesecake@lemmy.blahaj.zone 5 points 20 hours ago (1 children)

I guess you could install cockpit (via Terminal, sorry, but it's pretty straightforward and there are good guides). After that, you could use the cockpit web interface to deploy docker/podman containers. It's a bit clunky sometimes, but it does the job purely in UI.

You can also manage updates, backups, etc via cockpit if you install the required modules.

As base, I'd use any stable Linux distro that's reccomended for server use.

[–] techognito@lemmy.world 3 points 19 hours ago

https://cockpit-project.org/

for more info for those interested

[–] Hawk@lemmynsfw.com 3 points 19 hours ago (2 children)

I'm not trying to be unhelpful. My advice would be to steer into the terminal. Bite the bullet. I use arch and alpine for my servers but Fedora would be fine (but SELinux can be a pain with bund mounts)

Probably just go with Fedora with btrfs for snaps. It has lots of support and is a common choice for servers

[–] billwashere@lemmy.world 1 points 16 hours ago* (last edited 15 hours ago)

Yeah ~~kind of~~ totally agree. Trying to self host without using the terminal would be like trying to drive a car without touching the steering wheel with your hands. It’s possible but dangerous and cumbersome.

Don’t let it scare you. Get something installed to let you build some VMs to play around without worries (Virtualbox, VM Workstation, parallels), and install a distribution like Debian, Ubuntu, Mint and start to play. To self host all you really need is learning some basic file manipulation (move,copy,remove), how to edit text files (vi,emacs,nano), and the basic directory structure. That will get you 90% of the way there. When you see things like awk, sed, grep ask an AI to explain it, they are actually useful for that. These sort of commands start getting into advanced things like output redirection and regex which can be EXTREMELY confusing. Heck I have a CS degree, been in IT for almost 30 years, and I’ve been using Linux since the mid 90s and some of that still confuses me. So basically don’t fret if it’s too confusing, you are totally not alone. Play, screw up, try to fix it, curse, read a lot, try again, realize it’s toast, start over. Honestly I think I just described my job 😂

[–] Appoxo@lemmy.dbzer0.com 1 points 17 hours ago (1 children)

How do you troubleshoot Alpine? The one time I tried (later needed to use Debian because the OS was not supported) I could almost only find ressources in conjunction with containerization.

[–] Hawk@lemmynsfw.com 1 points 7 hours ago (1 children)

Honestly, I've had little trouble. The Gentoo Wiki and Void Handbook have a lot of overlap with OpenRC and musl, respectively.

While the documentation could be improved, the overall experience has been quite good and very stable.

[–] Appoxo@lemmy.dbzer0.com 1 points 7 hours ago

Maybe just a matter of skill issue with another distro (faimily).
Oh well. Maybe another time ;)

[–] EncryptKeeper@lemmy.world 6 points 1 day ago* (last edited 1 day ago) (1 children)

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.

load more comments (1 replies)
[–] hperrin@lemmy.ca 101 points 1 day ago* (last edited 1 day ago) (25 children)

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.

[–] Ulrich@feddit.org 1 points 6 hours ago (1 children)

It’s not as scary as people make it sound.

It is not "scary". It is complicated and requires special knowlege.

[–] hperrin@lemmy.ca 3 points 6 hours ago (1 children)

I wouldn’t call it complicated, but yeah, it’s special knowledge. So is all of self hosting.

[–] Ulrich@feddit.org 1 points 6 hours ago (1 children)

You wouldn't. A lot of tech people wouldn't. But it is. I've found this out the hard way, after spending dozens of hours trying to figure it out. You're not doing anyone any favors.

[–] hperrin@lemmy.ca 1 points 6 hours ago (1 children)

It’s not any more complicated than a GUI, it’s just that the dozens of hours you spent learning to use a GUI was a long time ago, and you don’t remember how complicated it was.

Also, you’re probably exaggerating, because dozens of hours is way longer than it should take to become proficient at the terminal. There are resources online that you can use to learn in a few hours.

[–] Ulrich@feddit.org -1 points 6 hours ago* (last edited 6 hours ago) (1 children)

it’s just that the dozens of hours you spent learning to use a GUI

This is utter nonsense. You do not need to learn to use a GUI. You just look at the available buttons and click the ones you need. And when you click them they do what they say, they don't return a "command not found" or "undefined error" with zero diagnostic information. And they work the same regardless of what OS or distro you're on.

The fact that you don't understand this is why you're not qualified to tell people that it's "not scary".

[–] hperrin@lemmy.ca 0 points 3 hours ago

Ok, so it’s been long enough for you, that you can’t even conceive of not knowing how to use a GUI anymore. Good for you, I guess.

[–] Mavytan@feddit.nl 8 points 19 hours ago (5 children)

Could you recommend a source for learning how to use the command line? In the past I struggled with understanding the basic commands and the various flags. I've found it difficult to find good documentation, but I would like to learn

[–] Nasan@sopuli.xyz 2 points 10 hours ago

This is a fun game approach to learning some bash basics.

[–] dgdft@lemmy.world 5 points 12 hours ago (2 children)

I highly recommend O'Reilly's Learning the Bash Shell in paperback form: https://www.oreilly.com/library/view/learning-the-bash/0596009658/.

The other responses you've received so far don't offer much insight into the historical background and underlying mechanics of the shell, which are crucial to understanding the "Why?"s of command-line quirkiness.

[–] Ulrich@feddit.org 1 points 6 hours ago (1 children)

A 20 year old paperback book seems like a bad choice.

[–] dgdft@lemmy.world 1 points 3 hours ago (1 children)

It's a 36 y/o language, mate. I still reference my copy all the time, and found it to be a great definitive resource when I was learning.

How many bash 4/5 features are you seriously using on a regular basis? What do you think is out-of-date?

[–] Ulrich@feddit.org 1 points 1 hour ago

Are you under the impression that that language hasn't changed?

[–] Mavytan@feddit.nl 3 points 12 hours ago

Thanks for your reply. I agree the 'why' is important, for me that usually makes things more intuitive

[–] hperrin@lemmy.ca 5 points 19 hours ago* (last edited 18 hours ago) (1 children)

It’s been a long time since I learned, so I don’t remember exactly what I used, but at a cursory glance, this one looks good:

https://www.terminaltutor.com/

Also, learning to read man pages will help a lot. Here’s an article on that:

https://itsfoss.com/linux-man-page-guide/

I do remember using “terminal cheat sheets” like this:

https://phoenixnap.com/kb/wp-content/uploads/2023/11/linux-commands-cheat-sheet-pdf.pdf

[–] Mavytan@feddit.nl 3 points 12 hours ago

Thanks for the very practical resources!

[–] LandedGentry@lemmy.zip 2 points 16 hours ago* (last edited 16 hours ago)

Find a problem or project that requires the terminal to solve it, follow the instructions laid out, and execute. Once you’ve done it, try tolook back at what you did and understand exactly what was going on under the hood. You can’t just “study terminal“ or something, the best way to learn is by doing. Just come up with simple things that need it. For instance, a Linux distribution that requires you to download a few drivers. That’s a really good building block right there. Gets you to understand how to navigate file paths on your computer from your terminal, how to know where to look for things and such

load more comments (1 replies)
load more comments (23 replies)
load more comments
view more: next ›