In this video I walk through Zammad, an open-source helpdesk/ticketing system you can self-host for your homelab—think “friends and family support desk” without paying for a SaaS. I show what the day-to-day flow looks like: dashboards, assigned vs unassigned tickets, taking ownership, setting priority/state, and the back-and-forth notes/replies (including the classic “have you tried restarting?” situation). I also demo the user side so you can see how simple it is to create a ticket and how public notes show up for the requester. Then I get into my actual setup workflow in my lab. I start with DNS (I manage zone files in GitLab and push them through a pipeline), add the new host to my Ansible inventory, and use AWX to run a workflow that builds the VM, patches it, installs Docker/Compose, and drops in Nginx as a reverse proxy. From there I follow the official Zammad Docker Compose install: clone the repo, copy env template, pin the version (I avoid the “-29” patch tag because I hit weird setup issues), and bring it up with `docker compose up -d` while tailing logs. Big takeaway: give the VM at least 4GB RAM because Elasticsearch can OOM, and don’t forget to switch the system HTTP type to HTTP behind your reverse proxy or you’ll run into CSRF token login errors.