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 3 weeks 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.
masterspace@lemmy.ca 3 weeks ago
Self hosting is doomed until this isn’t the answer.
atzanteol@sh.itjust.works 3 weeks ago
Yeah, this whole “Linux server” thing just isn’t going to take off.
baduhai@sopuli.xyz 3 weeks ago
It isn’t, self hosting just isn’t for everyone, and it never will be.
gravitas_deficiency@sh.itjust.works 3 weeks 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 running pfSense as my router that can support up to 10g (futureproofing).
aMockTie@lemmy.world 2 weeks ago
Imagine if OP asked: “I want to repair 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. Not for everyone, but enjoyable and generally optimized for those who participate.
hperrin@lemmy.ca 3 weeks 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.
irotsoma@lemmy.blahaj.zone 2 weeks ago
A desktop environment is a waste of resources on a system where you’ll only use it to install and occasionally upgrade a few server applications. The RAM, CPU power, and electricity used to run the desktop environment could be instead powering another couple of small applications.
Selfhosting is already inefficient with computing resources just like everyone building their own separate infrastructure in a city is less efficient. Problem is infrastructure is shared ownership whereas most online services are not owned by the users so selfhosting makes sense, but requires extra efficiencies.
Mavytan@feddit.nl 2 weeks ago
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 2 weeks ago
I highly recommend O’Reilly’s Learning the Bash Shell in paperback form: www.oreilly.com/library/view/…/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.
hperrin@lemmy.ca 2 weeks ago
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:
www.terminaltutor.com
Nasan@sopuli.xyz 2 weeks ago
This is a fun game approach to learning some bash basics.
RestrictedAccount@lemmy.world 2 weeks ago
TBF ChatHPT is probably your best bet
Angry_Autist@lemmy.world 3 weeks ago
The least sanctimonious linux shithead
Kusimulkku@lemm.ee 3 weeks ago
Name checks out
Ulrich@feddit.org 2 weeks ago
It is not “scary”. It is complicated and requires special knowlege.
hperrin@lemmy.ca 2 weeks ago
I wouldn’t call it complicated, but yeah, it’s special knowledge. So is all of self hosting.
VeganCheesecake@lemmy.blahaj.zone 2 weeks ago
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.