this post was submitted on 11 Jun 2024
75 points (96.3% liked)

Selfhosted

39964 readers
413 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 1 year ago
MODERATORS
 

I'm having trouble finding a proper starting point for self hosting, so I am curious on any resources you'd recommend, or even some build lists / pre-built devices.

What I want to do:

Important

  1. Host some applications like TinyTinyRSS, Jellyfin, GitLab, and Nextcloud which I'd want to be accessible in my home network
  2. Use the computer as a NAS to back data up and have it easily accessible on my desktop and laptop
  3. Have a piHole

Optional

  1. Access my hosted applications from outside of my network
  2. Use tools like Radarr to automatically download things from torrent lists
  3. Use it as a seedbox

The reason the last three are optional is because for that I'd have to expose the computer to the outside network, which has a whole bunch of benefits, but also a whole bunch of risks I am likely neither capable of nor comfortable with working around, so unless there's an easy fix (number 3 might be able to be handled via a VPN?) they're a problem for future me. For anything further I think I can just go from here once those requirements develop

I have already skimmed through some articles, watched some build guides for both NAS and home servers and honestly I just don't know what I need, both in information, hardware, and software.

  • Should I separate the NAS and Home Server, get a separate device for the piHole, or just have all three in one?
  • What hardware would be suitable for this?
  • Should I buy something off the shelf like a mini PC (for instance an Intel NUC) or one of these fancy prebuilt NAS devices where you just need to plug in some drives or build my own?
  • Would it be smarter to go with a Linux distro as the OS, for instance Debian, or should I use something like Unraid or TrueNAS which from what I can gather make setup more convenient and even handle docker images for you?

I am somewhat comfortable with Linux and the command line and have a budget of about 1000€, but if I can get away with less that would be great, and I can also stretch higher if needed for my requirements. I am also very new to self hosting and my networking knowledge is not non-existent, but limited.

I'm just a bit lost and would love some beginner-oriented resources or direct advice, thank you!

you are viewing a single comment's thread
view the rest of the comments
[–] ShepherdPie@midwest.social 2 points 4 months ago

You don't need to expose radarr/sonarr to the internet. Only your torrent client needs external access which would be routed through a VPN that offers port forwarding like AirVPN.

For hardware, I'm a big proponent of DIY. A NAS is very expensive and limiting since it has a fixed amount of bays. It's much more econonomial to buy a case that can hold a ton of drives like the Fractal Design Define series and then run your own hardware. I'd suggest 32GB of RAM, a modern i5 CPU with QuickSync (for Jellyfin), and a motherboard that has as many SATA ports as you can get. Check PCPartPicker to compare features and prices.

To run everything, you might look into using Proxmox and then running all your stuff off that in VMs or containers.

I'd probably keep PiHole separate since you only need a RPi3 and you don't want your whole network to go down if you restart the server. The rest can be run off the server.