Isaac (The Doc)
I am building my own lab, learning out loud, and turning the mess into something useful.
I am into the kind of work where the machine teaches you back: servers that overheat, containers that break, websites that need a real voice, AI tools that can either waste time or save a day, and photos that catch what the week felt like. The Doc Labs is where I keep all of it in one place.
This is not supposed to read like a polished company profile. It is my public notebook for the things I care about: homelab work, media servers, EmpireHub Pro, 3D printing, AI workflows, photography, experiments, mistakes, fixes, and the parts I am still figuring out.
I like coding, computers, infrastructure, and building things that probably should not exist until they suddenly do. That is the fun part for me: taking a rough idea, wiring it to real servers, testing it under pressure, and turning it into something I could actually use or sell.
Unraid, Jellyfin, Emby, Sonarr, Radarr, Immich, Pi-hole, backups, storage, and the real-life work of keeping the house stack running.
OpenClaw, voice notes, browser testing, research, code help, server checks, and practical agents that make my day less repetitive.
EmpireHub Pro, The Doc Labs, landing pages, field notes, ad ideas, and learning how to make rough ideas look and feel real.
Old photos, weekly albums, street shots, build pictures, visual references, and the personal taste that makes the site feel like mine.
I like understanding the real cause, not just restarting the container and pretending the problem went away.
Self-hosted photos, passwords, media, notes, automations, DNS, and dashboards matter because I want control over my own setup.
I care about turning rough ideas into real products, especially construction infrastructure like EmpireHub Pro that can become a business, not just a demo.
I like the strange projects: AI operators, server workflows, private dashboards, media systems, automations, and ideas that sound too extra until they start working.
The movie side is big enough that Radarr, Jellyfin, Emby, storage planning, backups, and cleanup workflows actually matter.
The TV library is the reason Sonarr, Prowlarr, Bazarr, download clients, and naming rules need to be documented instead of guessed.
At that size, a playback problem is not just “one app is bad.” It can be indexing, transcoding, storage, heat, scans, or the host itself.
That is why Immich and the photo approval workflow matter: there is enough history here to curate, not just dump everything online.
Unraid, Docker networking, fan control, temps, parity checks, media indexing, and how to spot when a problem is bigger than one app.
Using AI for code, server checks, transcription, browser audits, content planning, and clean daily workflows that actually save effort.
Photography albums, field notes, personal writing, short-form social ideas, and making the site sound like me instead of a template.
Follow along if you like real build notes: what worked, what broke, what I changed, what I am learning, and what I am probably rebuilding next.