I’m interested in exploring the world of self hosting, but most of the information that I find is incredibly detailed and specific, such as what type of CPU performs better, etc. What I’m really looking for is an extremely basic square 1 guide. I know basically nothing about networking, I don’t really know any coding, but it seems like there are a lot of tools out there that might make this possible even for a dummy like me.

Right now, my cloud computing is pretty much typical, I think. I use onedrive to sync my documents and old files. I need to be able to quickly access files on different devices, such as a powerpoint created on one device and presented on another. On my phone I use Android and my backups of downloads and photos and other data (messages, etc) are all on Google Drive /Google 1.

I’m willing to spend the time learning to an extent, but I’m not looking to become a network expert. I’m also willing to spend a little bit of money on hardware or a subscription service if necessary. Ideally I’d like to be out of this subscription service game, but the main goal is to be in charge of my own files. I have an old laptop running Linux to play around with and a fast and stable home internet connection.

Eventually, I would like to not only be syncing my files, photos, and documents in real time, but also I’d like to maybe try using it as an entertainment server to watch/listen to downloaded media on my home network.

Is there such a thing as a guide for a total beginner starting from zero? Is this worth attempting, or will I quickly find myself frustrated and in way over my head? Or, do I need to wait a little longer until more idiot-proof tools become available?

  • garibaldi@startrek.websiteEnglish
    1·
    10 months ago

    I’ve been meaning to write a guide like this but haven’t had a chance to complete it yet. In short, I’d recommend setting up an Ubuntu Server instance on some old hardware and using incus with ZFS to setup a separate container or VM for each service you want to run: https://linuxcontainers.org/incus/introduction/

    This way, if something doesn’t work out, you can just delete the container or VM. It also makes it easy to make snapshots or backups before you make a change (e.g. perform an upgrade) so you can easily roll back.

    You can even try incus online (see the above link) to get an idea of how it works.