this post was submitted on 28 Apr 2025
84 points (88.2% liked)

Selfhosted

46595 readers
1301 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 13 points 3 days 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.

[–] hperrin@lemmy.ca 104 points 5 days ago* (last edited 5 days ago) (30 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.

[–] Mavytan@feddit.nl 9 points 4 days 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

[–] dgdft@lemmy.world 6 points 4 days ago (9 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.

[–] Mavytan@feddit.nl 3 points 4 days ago

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

load more comments (8 replies)
[–] hperrin@lemmy.ca 5 points 4 days ago* (last edited 4 days 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 4 days ago

Thanks for the very practical resources!

load more comments (3 replies)
load more comments (29 replies)
[–] toynbee@lemmy.world 9 points 3 days ago

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

[–] groet@feddit.org 46 points 5 days ago (1 children)

Generally, Linux Servers are best administered from a command line. At least in the beginning to set everything up. In turn they are faster on lower hardware as they dont even have a graphical desktop at all so need less resources. You could of course install a windows server OS. They can be fully administered through Remote Desktop and a GUI.

There are multiple projects to make self hosting more accessible (like casaOS). They automate many steps of the setup and then offer you a webUI for further steps. Maybe have a look here https://github.com/awesome-selfhosted/awesome-selfhosted?tab=readme-ov-file#self-hosting-solutions

[–] scheep@lemmy.world 17 points 5 days ago (1 children)

Woah, there's a lot. Nice that there's plenty of options!

load more comments (1 replies)
[–] Andromxda@lemmy.dbzer0.com 28 points 5 days ago (6 children)
[–] dmention7@lemm.ee 8 points 5 days 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.

load more comments (5 replies)
[–] Ulrich@feddit.org 4 points 3 days ago
[–] Appoxo@lemmy.dbzer0.com 6 points 4 days ago* (last edited 2 days 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 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 3 points 3 days 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.

[–] pHr34kY@lemmy.world 19 points 5 days ago (1 children)

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 5 points 4 days ago (1 children)

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.

load more comments (1 replies)
[–] q7mJI7tk1@lemmy.world 11 points 4 days ago* (last edited 3 days 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.

[–] VeganCheesecake@lemmy.blahaj.zone 5 points 4 days 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.

load more comments (1 replies)
[–] EncryptKeeper@lemmy.world 6 points 4 days ago* (last edited 4 days 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)
[–] Guenther_Amanita@slrpnk.net 13 points 5 days ago* (last edited 5 days ago) (4 children)

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

load more comments (4 replies)
[–] AustralianSimon@lemmy.world 4 points 4 days ago

Mint or Ubuntu is like Windows but better.

[–] scheep@lemmy.world 10 points 5 days ago (2 children)

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

load more comments (2 replies)
[–] dave@lemmy.wtf 3 points 4 days ago* (last edited 4 days 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

[–] testman@lemmy.ml 10 points 5 days 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.

[–] glitching@lemmy.ml 9 points 5 days ago (1 children)

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.

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