<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>WP-CLI on Luis Sousa Blog</title>
		<link>https://blog.nuvai.cloud/tags/wp-cli/</link>
		<description>Recent content in WP-CLI on Luis Sousa Blog</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Sat, 13 Jun 2026 11:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://blog.nuvai.cloud/tags/wp-cli/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Three Reboots in One Afternoon: Guardrails for Bulk WP-CLI on Docker WordPress</title>
				<link>https://blog.nuvai.cloud/posts/bulk-wp-cli-guardrails-three-reboots/</link>
				<pubDate>Sat, 13 Jun 2026 11:00:00 +0000</pubDate>
				<guid>https://blog.nuvai.cloud/posts/bulk-wp-cli-guardrails-three-reboots/</guid>
				<description>&lt;p&gt;An AI agent running Semrush SEO fixes is a wonderful thing — until your Oracle VM stops answering SSH and you reboot for the third time before lunch.&lt;/p&gt;&#xA;&lt;p&gt;That happened on our travel blog (&lt;a href=&#34;https://joyofexploringtheworld.com/&#34;  class=&#34;external-link&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;joyofexploringtheworld.com&lt;/a&gt;): a 23 GB RAM host running WordPress in Docker with two web replicas, MariaDB, Redis, Traefik, imgproxy, Datadog, CrowdSec, and a steady stream of &lt;code&gt;docker compose run --rm wpcli&lt;/code&gt; invocations. The site was fine. The &lt;strong&gt;host&lt;/strong&gt; was not.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
