So after months of dealing with problems trying to get the stuff I want to host working on my Raspberry Pi and Synology, I’ve given up and decided I need a real server with an x86_64 processor and a standard Linux distro. So I don’t continue to run into problems after spending a bunch more, I want to seriously consider what I need hardware-wise. What considerations do I need to think about in this?

Initially, the main things I want to host are Nextcloud, Immich (or similar), and my own Node bot @DailyGameBot@lemmy.zip (which uses Puppeteer to take screenshots—the big issue that prevents it from running on a Pi or Synology). I’ll definitely want to expand to more things eventually, though I don’t know what. Probably all/most in Docker.

For now I’m likely to keep using Synology’s reverse proxy and built-in Let’s Encrypt certificate support, unless there are good reasons to avoid that. And as much as it’s possible, I’ll want the actual files (used by Nextcloud, Immich, etc.) to be stored on the Synology to take advantage of its large capacity and RAID 5 redundancy.

Is a second-hand Intel-based mini PC likely suitable? I read one thing saying that they can have serious thermal throttling issues because they don’t have great airflow. Is that a problem that matters for a home server, or is it more of an issue with desktops where people try to run games? Is there a particular reason to look at Intel vs AMD? Any particular things I should consider when looking at RAM, CPU power, or internal storage, etc. which might not be immediately obvious?

Bonus question: what’s a good distro to use? My experience so far has mostly been with desktop distros, primarily Kubuntu/Ubuntu, or with niche distros like Raspbian. But all Debian-based. Any reason to consider something else?

  • Zagorath@aussie.zoneOP
    link
    fedilink
    English
    arrow-up
    1
    ·
    3 days ago

    I’m not sure I agree with your definition of walled garden. I’d say it’s a place that’s designed to be nice and easy to use within the bounds designed for you (the garden), but which protects the user from doing something that might harm them, even if that “protection” comes at the cost of being able to do other things they want to do, in a kind of paternalistic way (the wall). The classic example would be iOS, where the only apps you can install are the ones Apple has approved for you. Getting apps from the open web the way you would on Windows, macOS, or Linux could be dangerous!

    Your description of:

    you may run into roadblocks doing things that way, yes. You are pretty much limited to what’s on their (vast) catalog

    Makes it sound very much a walled garden to me. Not as high-walled as iOS of course, but it’s a spectrum.

    But anyway, it’s basically semantics. Not that important what you call it.