Hi all, some months ago I had an accident that required surgery, long story short, found this sub and it helped me go through the slow recovery process. I have been learning a lot with you and now I want to share my experience so far, I put together a post about self-hosting my website at home, the hardware I’m using, the software, tools, etc. I hope you find it useful or even inspirational if you haven’t started yet, and I would love to hear your comments.

https://proderror.eu/blog/self-hosting-my-website-at-home-2023-11-25.md

​

    • Nintenuendo_@alien.topBEnglish
      1·
      10 months ago

      Why cloudflare tunnels? If you already have a domain, and are going to use cloudflare, why add their dns nameservers to your registrar admin page, and use their dns for free?? That solves the issue of hosting at home and showing your ip to the world via any method using your domain name, all they’ll see is cloudflare.

  • Nintenuendo_@alien.topBEnglish
    1·
    10 months ago

    Very cool site! You’re so right, hosting at home is so fun and actually super useful! My setup is soooo much easier to access and control now, and I’ve learned so much.

    My self hosted site is at https://nintenuendo.tv heh, cheers to many more years of open-source!

      • Nintenuendo_@alien.topBEnglish
        1·
        10 months ago

        for the shell, that’s an easy one, shellinabox, with a custom dark mode.

        for the exposed services you describe, none are “exposed”, they are hosted in nginx (meant to face the WAN, subdomained and not port forwarded) with fail2ban setup for custom filtering, and beyond that are proxied through cloudflare and their filtering for ddos etc. Most of my services are behind htpasswd hashed/salted pw’s or ldap (right now just htpasswd for the local site), and the ones that arn’t use token logins like plex, overseerr, etc. I’ll be ok :)