What I am studying
Linux, Unraid, Docker, WordPress, local AI, security basics, photography, and the practical details I am learning while I keep my own setup alive.
Live from the lab
This is my public command center: photos I want to keep, homelab fixes I had to learn the hard way, AI operator work, container notes, product experiments, and the lessons I am picking up while I build in public.
Creator command center
I want people to understand the person behind the rack, not just the services running on it.
Weekly albums, old shots, street photos, build pictures, and anything worth keeping in public.
aboutWho I am, what I care about, what I am learning, and why I keep building this stuff in public.
learningLinux, containers, AI agents, websites, security basics, photography, and the systems behind the work.
ai tasksVoice notes, website builds, server checks, research, automations, browser testing, and ad prep.
Personal operating system
This is my living now layer: what I am studying, what I am building, and what is changing in the lab.
Linux, Unraid, Docker, WordPress, local AI, security basics, photography, and the practical details I am learning while I keep my own setup alive.
EmpireHub Pro, my homelab stack, OpenClaw workflows, media automation, photo albums, and small utilities that solve problems I actually run into.
Server checks, code review, browser testing, content research, voice-note cleanup, automation planning, and turning rough ideas into working pages.
Lab status, public-safe
I can talk about what is running, what got paused, and why a service changed while keeping private infrastructure details off the public internet.
I write public-safe updates about Jellyfin, Emby, Sonarr, Radarr, and the library fixes without exposing private paths, keys, or live ports.
I keep track of why something was shut off, what broke, and what I need to check before turning it back on.
Short posts for ideas, frustrations, rebuild plans, photography thoughts, and product lessons before they become polished articles.
Featured work
These are the builds that make the rest of my site make sense: my infrastructure, my AI tooling, and my product work from the same desk.
My production rack behind Jellyfin, Emby, Sonarr, Radarr, Immich, Vaultwarden, backups, and the checks that keep it sane.
AI operationsMy AI operator setup for servers, Telegram, web audits, browser checks, automations, and practical day-to-day support.
Product buildReal deployment notes from a construction software product: design passes, analytics fixes, production builds, and hard lessons.
Personal layer
I want this lab to show the person behind the rack: old photos, rough notes, desk experiments, prints that worked, posts about containers, and thoughts that sound like they came from me, not a brand department.
Upload photos as Gallery Items, group them with Gallery Categories, and turn each week into a small visual log.
StoryA dedicated page for who I am, what I am into, what I am learning, and why the lab exists.
Mind logShort updates can capture the week: what changed, what broke, what got fixed, what annoyed me, and what is next.
Social bioUse this for TikTok, Instagram, and other profiles to point people toward EmpireHub Pro, projects, photos, and the community.
Current statusA live snapshot of the current studies, active builds, AI workflows, and next notes to publish.
Explore
Current operating picture
Server map
I keep private URLs, ports, keys, and paths off the site, but the shape of the lab should be clear: one host serves the public site and apps, Tower handles media and archive work.
The host behind The Doc Labs runs WordPress, Nginx, MariaDB, Nextcloud, n8n, NocoDB, Open WebUI, Portainer, Uptime Kuma, RSSHub, Homarr, Minecraft Bedrock, TheDocBot, Watchtower, and supporting databases/cache containers.
Tower runs the media side: Jellyfin, Emby, Sonarr, Radarr, Prowlarr, qBittorrentVPN, SABnzbdVPN, Bazarr, Jellyseerr, Flaresolverr, Immich, Vaultwarden, Watchstate, Cloudflared, and PostgreSQL support services.
The current library snapshot is about 645 movie video files, 246 TV show folders, about 15,900 TV/video files, and about 18,262 photo files. That is why I document updates, scans, heat, storage, and playback issues.
The site should explain what each service does, why I use it, what broke, and what I learned. It should not publish live admin links, ports, private paths, keys, tokens, or anything that makes the rack easier to attack.
Latest notes
Plex is the media server most people recognize first, but it is not the main one I am using in The Doc Labs right…
Read postA detailed first-person operating guide for Jellyfin: why I use it, how I set it up, day-to-day use, notifications, monitoring, security, and recovery.
Read postA detailed first-person operating guide for Emby: why I use it, how I set it up, day-to-day use, notifications, monitoring, security, and recovery.
Read postDiscord community
I use the community for homelab help, project threads, AI workflow notes, and build talk with people who actually ship things.