Web Form to CRM in Two Seconds: Wiring Wix, n8n, Mailgun and Odoo 18 (and a Bug That Hid for Seven Weeks)
I am a one-person consultancy. One of my clients is a sign shop whose quotes, leads and invoices live in a single self-hosted Odoo 18 instance on a small VPS, which is the source of truth for both my company and theirs as two companies in one database. The automation glue is n8n (2.x, Postgres 17, pinned images) in Docker on the homelab AI box .62, reachable from the internet only through a Cloudflare Tunnel on a dedicated webhooks hostname. Outgoing mail goes through Mailgun; pushes land on my phone through ntfy.
This post is not a tutorial on any one product. It is the plumbing between them, and it is three bugs that each took a real lead or a real week to surface: a DMARC policy that bounced the very first email about a new lead, an inbound-mail route that would have silently eaten every reply, and an n8n trap I want to tattoo somewhere, where a scheduled job failed every morning for seven weeks while the identical workflow passed every time I ran it by hand.
Everything here is exported into an infra-as-code repo, in the spirit of my earlier write-up on backing up a homelab as code, so none of this is a story about remembering how it was set up. It is the story of what the plumbing does, and the three places it quietly broke.
Teaching an AI to Develop My RAW Photos: A Self-Hosted Linux Pipeline
I wanted to answer a specific question: could an AI agent do the boring, careful parts of my photography workflow — the parts I actually skip because they take too long?
Not “make my photos look good” in the Instagram-filter sense. I mean the tedious, correct-but-thankless work: pulling the right RAW off my server, applying the exact lens-correction data for the exact lens I used, denoising only the frames that need it, keeping the EXIF intact, filing everything under the right date, and getting a print onto photo paper without fighting a driver. The stuff a careful darkroom tech would do and a busy human never quite gets around to.
So I built it. A local, self-hosted pipeline where Claude Code can reach into my Immich library, pull original Canon CR3 RAW files, develop them in darktable with camera- and lens-specific corrections, retouch in GIMP, print on a networked Canon photo printer, and push finished JPEGs back into Immich as new assets — all driven through the Model Context Protocol (MCP).
After the Rip: Auto-Naming a Home Media Library for Jellyfin with Python, TMDB, and ffprobe
Getting video off a disc is the part everyone talks about. The part that actually eats your evenings is everything after: a folder full of title_t00.mkv, disc1/, C3_t01.mkv files that mean nothing to a media server. Jellyfin wants very specific names and folder layouts, and if you don’t give them to it, you get “Unknown Movie,” mismatched episodes, and bonus features scattered as phantom entries.
So I extended a post-processing step into a proper Python pipeline that takes whatever came out of my ripping setup and turns it into a Jellyfin-perfect library: correct movie names with IMDb IDs, TV episodes matched to the right SxxExx, extras bucketed into the folders Jellyfin recognizes, then rsynced to the NAS and scanned in — with an ntfy ping at the end. This post is about that pipeline. It is deliberately not about disc decryption — it starts the moment you have plain .mkv files.