Decoupling AI Automation from WordPress: Designing Async HTTP REST Workers
A practical architecture for running long AI workflows beside WordPress, with asynchronous REST workers that keep publishing responsive.
Topic
All articles
A practical architecture for running long AI workflows beside WordPress, with asynchronous REST workers that keep publishing responsive.
A WordPress REST API request can report that Basic Authentication is required even after HTTP authentication was disabled. That message does not prove that WordPress itself is demanding a Basic Auth header. The challenge may come from a browser…
Gemini can make a WordPress workflow genuinely useful: classify uploaded files, summarize support tickets, generate structured editorial drafts, or answer questions about a site’s own documentation. The difficult part is not sending the first request. The difficult part is…
Cloudflare is usually introduced as a performance and security layer for WordPress. It can cache static assets, reduce connection latency, absorb common attacks, and provide useful visibility into how visitors reach a site. Typography is part of the same…
Adding Gemini or another AI model to a WordPress plugin is easy to demonstrate and surprisingly difficult to operate. A successful request in development does not prove that the feature is safe in production. Models can return invalid JSON,…
Hosting support is diagnosis at scale — and most of it follows patterns. Here's an architecture that pairs Gemini's reasoning with Ansible's safe execution to triage server issues faster, without ever letting the model touch a shell.
Same Gemini models, two very different doors. A practical guide to what actually changes on Vertex AI — auth, quotas, governance — and a checklist for knowing when the move is worth it.
Cleaning a hacked WordPress site means reading hundreds of flagged files under time pressure. Here's how Gemini works as a triage assistant — the workflow, the prompt design, the structured verdict schema, and the hard limits on trusting it.
Google's open Gemma models run on your own hardware — no API key, no per-token bill, no content leaving your machine. Here's a practical local setup with Ollama and where it genuinely beats the hosted API for WordPress work.
Most model-choice advice is vibes. Here's a decision framework for Flash vs Pro in content workloads, plus a benchmark harness you can run against your own pipeline in an afternoon.