this post was submitted on 28 Apr 2025
75 points (87.1% liked)

Selfhosted

46407 readers
958 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?

you are viewing a single comment's thread
view the rest of the comments
[–] thefartographer@lemm.ee 4 points 1 day ago

Just from the handful of OSs I've tried, I'd suggest Ubuntu desktop again.

As for docker, I'd say to get docker and docker compose setup. Once you're running in docker compose, adding machines is often as simple as editing some markup in a text editor.

But my final suggestion is to crawl before you walk before you run. Start slow in the terminal. Instead of using your file explorer, navigate directories using the terminal and then open the directory you need into the file explorer using the terminal.

Want a new file? Use touch. Want a new directory? Use mkdir. Eventually, it'll become annoying to open a file from your explorer when you could just open it from the terminal. Then, you'll get annoyed with text editors and want to reduce your context switches by using vim.

Also, --help is your best friend when trying to figure out commands. You got this! Feel free to send me a message if you wanna chat and have any questions when you're ready to start dipping your toes. I'm far from an expert, but I've made some progress of my own and eventually we might learn a thing or two together.