• 1 Post
  • 13 Comments
Joined 6 months ago
cake
Cake day: March 27th, 2024

help-circle
  • arcayne@lemmy.todaytoSelfhosted@lemmy.worldDNS?
    link
    fedilink
    English
    arrow-up
    1
    ·
    6 days ago

    My preferred way of solving this is to run a PowerDNS cluster with DNSDist and keepalived. You get all the redundancy via a single (V)IP.

    Technitium is probably more user friendly for greenhorns, though… and offers DHCP too. Beats pihole by a mile.



  • Wezterm is my primary. Love the built-in domain/sshmux features, especially for work. The LUA config rocks, sky is the limit. Highly portable when using something like Chezmoi or YADM.

    That said, it’s not always the most performant, especially with certain TUIs. I’ve been running my NVim workspace in Kitty lately just to avoid the minor UI lag (primarily with lazygit). Not a fan of Kitty (or its dev) otherwise, but it serves its purpose.

    If Wezterm ever gets optimized, it’ll be the GOAT for me.

    Ghostty also sounds like it’s got potential, but haven’t gotten my invite yet. ¯_(ツ)_/¯







  • Apps: SSO via Authentik where I can, unique user/pass combo via Bitwarden where I can’t (or, more realistically, don’t want to).

    General infra: Unique RSA keys, sometimes Ed25519

    Core infra: Yubikey

    This is overkill for most, but I’m a systems engineer with a homelab, so it works well for me.

    If you’re wanting to practice good security hygiene, the bare minimum would be using unique cred pairs (or at least unique passwords) per app/service, auto-filled via a proper password manager with a browser extension (like KeePassXC or Bitwarden).

    Edit: On the network side, if your goal is to just do some basic internal self-hosting, there’s nothing wrong with keeping your topo mostly flat (with the exception of a separate VLAN for IoT, if applicable). Outside of that, making good use of firewalls will help you keep things pretty tight. The networking rabbit hole is a deep one, not always worth the dive unless you’re truly wanting to learn for the sake of a cert/job/etc.



  • We’re so tightly integrated with the M$ ecosystem at my work, it’s painful. My department has even been going out of it’s way to self host (F)OSS alternatives where we can, just to avoid as much of the cludge as possible.

    Has anyone tried out the new Teams integration feature that Mattermost recently rolled out for Enterprise customers? If so, any good?

    If we can seamlessly sync calls/meetings from Teams into Mattermost and ditch the Teams client for our day-to-day comms, I might have a fighting chance at convincing my supervisor to pivot my department.