cross-posted from: https://lemmy.ml/post/24823173

Hi folks, looking for a bit of steer to get off the ground with self hosting. My goals to start with are pretty straight forward:

  • I want to set up Home Assistant to move my smart devices off the cloud and fully contained within the walls of my home.
  • I want to set up my own little Pixelfed server for my family’s use, along with some other federated socials.

From what I was looking at, I think my easiest route to doing both of these things is with a Home Assistant Yellow (built-in Zigbee and Thread system) with a Raspberry Pi 4.

I’ve never done anything like this before but I’m interested in learning. If anyone more experienced has any insight or direction, I’d really appreciate it! Cheers!

  • tofuwabohu@slrpnk.netEnglish
    5·
    2 days ago

    You got quite good answers already, here and in the other thread.

    My suggestion is to not start with pixelfed but something else (simple stuff like dokuwiki, you can use it to document your stuff while you’re at it) to get an understanding of the whole process (running the service itself, making it available to the internet after hardening your infrastructure a bit etc).

    Also, if you’re not settled for how to do it exactly, give Docker a try. There’s a reason it’s popular among selfhosters!

    • Sai@lemmy.mlOPEnglish
      2·
      2 days ago

      Yeah I’ve been doing some reading and have seen Docker mentioned a good bit. I think I just needed some goals to start with, I’m sure I’ll take a roundabout route to get there and all some new goals once I have those two done!

      When you say “hardening my infrastructure” you mean suring up the security, yeah? Also something I need to add to the list to learn about!

      • tofuwabohu@slrpnk.netEnglish
        2·
        2 days ago

        Yes! Mostly having a plan on how to make your service reachable in the internet while keeping the rest of your local stuff shutdown.

        Many people recommend cloudflare, but I don’t think it’s necessary. If you get a public IP from your ISP, it’s relatively easy with dyndns. Personally, I have a virtual machine running nginx as a reverse proxy and configured the router to forward port 80 and 443 to that machine.

        • Sai@lemmy.mlOPEnglish
          2·
          2 days ago

          Cool! Good to know! Will definitely be back to this post to follow up once I make some prog!