A simple question to this community, what are you self-hosting? It’s probably fun to hear from each-other what services we are running.

Please mention at least the service (e.g. e-mail) and the software (e.g. postfix). Extra bonus points for also mentioning the OS and/or hardware (e.g. Linux Distribution, raspberry pi, etc) you are running on.

  • terribleplan@lemmy.nrd.liEnglish
    9·
    2 years ago

    In various clouds

    • Email - Docker Mail Server (Postfix, Dovecot, Rspamd, etc.)
    • Reverse Proxy cluster - frp
      • This is actually pretty neat. It is basically acting as a self-hosted ngrok, letting me expose all the stuff in my homelab without having to put my home IP out there.
    • External Monitoring - Uptime Kuma
    • Random sites via cloudflare workers/R2

    In my homelab

    Infrastructure

    • DNS - PiHole fronting local Unbound resolvers
    • Load Balancing/Routing - Traefik
    • Storage - Gluster exposed via Samba
      • I am still searching for the right solution for storage… nothing does what I want. I have been slowly writing my own, but don’t have the time to get it to a point I trust it, haha.
    • Custom traefik auto-config clients/server
      • Reads labels on containers and announces them to the server that traefik uses for HTTP service discovery
    • Custom docker-compose nonsense
      • Basically lets me choose where to run docker-compose files in a simple and centralized way, including on multiple machines
      • Doesn’t do scheduling/monitoring/etc, just manually setting “this compose should run these machines”
      • I got tired of running k8s and nomad.

    Services

    • Authentication - Authentik
    • Media - Jellyfin
    • Minecraft
    • Password Manager - Vaultwarden
    • PKM - DokuWiki
    • SCM - Forgejo (a fork of Gitea, which itself is a fork of Gogs)
    • Social Media - Lemmy
    • Webmail - Snappymail
    • Several random little websites
    • Many little things I’ve written for myself

    Any service that needs non-http traffic pointed at it runs local instances of the frp client to expose that port to the reverse-proxy cluster.