this post was submitted on 10 Jun 2026
93 points (97.9% liked)

Selfhosted

60366 readers
671 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
93
I need a map... (lemmy.world)
submitted 3 weeks ago* (last edited 3 weeks ago) by Snapz@lemmy.world to c/selfhosted@lemmy.world
 

There are so many options to get started with self hosting that I feel myself stuck in the "paralysis of choice". For a novice, does anyone have a good resource for the equivalent of good/better/best paths that cover the "basics" (In my mind this is hosting images, music, video, connected home controls, search and email)?

Thinking something like first try path A, if you feel comfortable and your HW can handle A, then try path B, etc. I guess a it of a tutorial mode feeling where you get exposed to key boxing blocks initially and then you are released into the large open world on your own.

I know the advantage of this movement is the choice and the well distributed variety, but just feels hard to start.

I have an old laptop, an SFF workstation and a NAS to play with.

Any suggestions?

Edit: Thank you all for a very generous response. I knew this was a tough ask from the start because, by design, this area is vast and constantly evolving. A lot of great starting points here that I'm now considering.

you are viewing a single comment's thread
view the rest of the comments
[–] L7HM77@sh.itjust.works 3 points 3 weeks ago

Get a cheap pcie 1Gbit Intel NIC from ebay, cheap switch, Ethernet cables.

Throw the NIC and proxmox into the SFF, make a VM for OPNsense, use the switch downstream from the SFF. Get the NAS and laptop onto a separate LAN firewalled from the ISP.

Set up another VM in proxmox for a workspace, connect it to the NAS file shares, do the same with the laptop. Set up syncthing on laptop, workspace VM, and the NAS if it supports it. Make a keepass database, start organizing all logins to keepass, keep everything synchronized with syncthing.

Set up tailscale, add it into OPNsense to allow easy and secure(?) remote access into your subnet. (I use tailscale, but don't trust them much and want to switch away.)


Its very daunting at first, but this is the path I took, not really a guide. All this will take a few days of constant effort to get right, but you absolutely don't need to do everything at all once, just a slow migration. I've been slowly building mine up for about 5 years now, and there is no one "right" answer to anything.

Only move forward when you get comfortable with each step. I personally run everything from a stack of thin clients I got from some kid off Craigslist. Think they came out of a bar and grill, filled with grease and cigarette tar, but they cleaned up nice. A full Arr stack with jellyfin runs great on an Intel 6500t with 16gb DDR3 ram.

Slowly get comfortable with the CLI and general security updates, next thing you know you'll have 3x smart switches, better/faster NICs for the proxmox box, a WIFI6 AP for better throughput. Its endless. I try to focus on minimal wattage, my full stack pulls a steady 80 to 100 watts 24/7. You'll get a "gut" felling for what runs best on what hardware. I spent too much on Raspberry Pi's in the past, should've tried thin clients sooner.