Hey everyone! I’m sort of still green for selfhosting, but I wanted to share my setup so far:

The following services are selfhosted in docker

  • Audiomuse (smart music tagging, mood based and all that)
  • Navidrome for music hosting
  • Jellyfin for TV shows (not a lot) and Films (not a lot again, but steadily increasing)
  • Radicale for serving contacts/TODOs/calendar
  • SFTPGo to act as my drive
  • Kavita for ebooks and manga (I have tons of both)
  • Glance for homepage
  • forgejo for git forge hosting

The system specs are kind of visible in the homepage, so I won’t spell them out here again. Mostly an old optiplex running arch, though I want to change it to nixos later on.

System tools:

  • nushell for shell
  • calibre for ebook management and tagging + fanficfare plugin to download fanfictions
  • Caddy for reverse proxy (so I don’t have to remember ports)
  • netbird for VPN (also because it allows me to set wildcard DNS resolution for nodes, so I don’t have to set up a dedicated pi-hole or adguard)
  • Handbrake and ffmpeg for processing videos and such
  • beets for tagging music
  • a sysinfo script to generate system information for glance to consume
  • Probably other things too, I’m forgetting

Everything is accessible only via netbird, and external inbound connections are firewalled off

Apart from that, I eventually plan on adding the following as well:

  • Immich for photo hosting
  • Vaultwarden for passwords
  • Gollum (still debating on alternatives) for a webUI for my notes
  • Paperless-NGX

I’m still thinking on more that I can add. Note that whatever I add should not need an inbound connection/stable IP address, since I don’t intend to expose the server to the public. Any suggestions/tips? Thanks!

UPDATE: Forgot to add, I’d probably add homebox too, for inventory management 😅

UPDATE 2: I’m silly, I forgot that I’m also looking into self-hosted RSS feed readers 😆

  • ExLisper@lemmy.curiana.netEnglish
    3·
    1 day ago

    Also, vaultwarden requires HTTPS?? Ah drat, that’s not good :/ I don’t have experience with that.

    Yes, the clients work only over HTTPS. Caddy can handle that:

    vaultwarden.cosmos.internal {
        tls /opt/caddy/certificate.crt /opt/caddy/private.key
        handle /* {
                reverse_proxy http://localhost:8081/
        }
}

    The certs need to be generated for this specific domain:

    openssl req   -x509   -newkey rsa:4096   -keyout key.pem   -out cert.pem   -sha256   -days 36500   -nodes   -subj "/C=XX/ST=StateName/L=CityName/O=CompanyName/OU=CompanySectionName/CN=cosmos.internal"

    Some more details are here: https://bitwarden.com/help/certificates/ under “Using a self-signed Certificate”