Pasture: WordPress pinned with its updates off, Mbin's worker restarting, threads checking our own deliveries

A full sweep found three peers silent. WordPress had updated itself to 7.1.2 from WP-Cron, and the new CA bundle dropped
Caddy's root: it now runs the 7.1.2 image with automatic updates off. Mbin's messenger worker had died when the shared
Postgres restarted under it: it now consumes again whenever it stops. Friendica sat in a quarantine left by the old
breaker. The threads scenario checks that PrivaPub never sends carol's reply to Mastodon, since a relay Mastodon has just
left (the relay scenario's) may still pass it on. With these, every scenario passes but the crawler's, which needs it
switched on.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LsXgEaXee4GCU1hwYgPJXw

tools/pasture/peers/mbin.sh

@@ -82,8 +82,7 @@ mbin_up() {
 		podman logs pasture-mbin 2>&1 | grep -q "PHP app ready" && break
 		sleep 2
 	done
-	podman run -d --replace --name pasture-mbin-worker "${common[@]}" "$MBIN_IMAGE" \
-		php bin/console messenger:consume scheduler_default old async outbox deliver inbox resolve receive failed --time-limit=86400 >/dev/null
+	mbin_worker
 	for _ in $(seq 1 60); do
 		site mbin.test -s -o /dev/null -w '%{http_code}' https://mbin.test:6443/api/instance 2>/dev/null | grep -q 200 && break
 		sleep 2
@@ -102,3 +101,11 @@ mbin_settle() {
 	mbin_console mbin:user:verify mbuser >/dev/null 2>&1 || true
 	python3 "$here/peers/mbin_token.py" "$MBIN_PASSWORD" "$here/.state/mbin/client.json" > "$here/.state/mbin.token" 2>"$here/.state/mbin/token.log" || true
 }
+
+# mbin_worker: the messenger worker, consuming again whenever it stops (an hour's time limit, or a lost database: a
+# Postgres restarted once left Mbin sending nothing for a day)
+mbin_worker() {
+	podman run -d --replace --name pasture-mbin-worker "${common[@]}" "$MBIN_IMAGE" sh -c 'while :; do
+		php bin/console messenger:consume scheduler_default old async outbox deliver inbox resolve receive failed --time-limit=3600; sleep 5
+	done' >/dev/null
+}

tools/pasture/peers/wordpress.sh

@@ -1,10 +1,11 @@
-# WordPress 6 with the ActivityPub plugin 9.3.1: posts as Articles (or Notes when short), comments as replies, each
+# WordPress 7.1.2 with the ActivityPub plugin 9.3.1: posts as Articles (or Notes when short), comments as replies, each
 # author an actor and the blog one too, likes and boosts kept as comments of their kind. On a shared MySQL 8.4 (database
 # wordpress). The plugin federates from WP-Cron, so a sidecar runs the due events every few seconds. WordPress sends its
 # requests through its own CA bundle (wp-includes/certificates), to which Caddy's root is appended; its URL guard refuses
 # private addresses with no switch, which the pasture's public-looking subnet passes. The admin is wpuser; the town's
-# accounts are authors with application passwords for the REST API.
-WORDPRESS_IMAGE=${WORDPRESS_IMAGE:-docker.io/library/wordpress:6-apache}
+# accounts are authors with application passwords for the REST API. Its automatic updates are off: one (core 7.1.2,
+# 2026-10-05) wrote a new CA bundle over the one Caddy's root was appended to, and nothing reached PrivaPub after it.
+WORDPRESS_IMAGE=${WORDPRESS_IMAGE:-docker.io/library/wordpress:7.1.2-apache}
 WORDPRESS_CLI_IMAGE=${WORDPRESS_CLI_IMAGE:-docker.io/library/wordpress:cli}
 WORDPRESS_ACTIVITYPUB=9.3.1
 WORDPRESS_PASSWORD=Wordpress-Pasture-1
@@ -24,7 +25,7 @@ wordpress_up() {
 	# behind Caddy: https as the proxy says, and the site's own address
 	local extra="if (isset(\$_SERVER['HTTP_X_FORWARDED_PROTO']) && \$_SERVER['HTTP_X_FORWARDED_PROTO'] === 'https') { \$_SERVER['HTTPS'] = 'on'; }
 define('WP_HOME', 'https://wordpress.test'); define('WP_SITEURL', 'https://wordpress.test'); define('DISABLE_WP_CRON', true);
-define('FS_METHOD', 'direct');"
+define('FS_METHOD', 'direct'); define('AUTOMATIC_UPDATER_DISABLED', true); define('WP_AUTO_UPDATE_CORE', false);"
 	podman run -d --replace --name pasture-wordpress --network $net \
 		-e WORDPRESS_DB_HOST=mysql -e WORDPRESS_DB_USER=pasture -e WORDPRESS_DB_PASSWORD=pasture -e WORDPRESS_DB_NAME=wordpress \
 		-e WORDPRESS_CONFIG_EXTRA="$extra" -v pasture-wordpress-html:/var/www/html -v "$ca:/pasture/ca:z,ro" \

tools/pasture/scenarios/threads.sh

@@ -23,7 +23,9 @@ root=$(curl -s -X POST -H "Authorization: Bearer $AT" "$P/api/v1/statuses" -d "s
 root_uri=$(echo "$root" | j "print(d['uri'])")
 reply_uri=$(curl -s -X POST -H "Authorization: Bearer $CT" "$P/api/v1/statuses" -d "status=an answer from carol $run&visibility=public&in_reply_to_id=$(echo "$root" | j "print(d['id'])")" | j "print(d['uri'])")
 until_true 45 '[ "$(m_rails "puts Status.exists?(uri: \"$root_uri\")")" = "true" ]' && ok "alice's post reaches Mastodon" || ko "alice's post never reached Mastodon"
-[ "$(m_rails "puts Status.exists?(uri: \"$reply_uri\")")" = "false" ] && ok "carol's reply is not delivered there" || ko "carol's reply reached Mastodon unasked"
+# (PrivaPub never sends it there; a relay Mastodon has just left, in the scenario before, may still pass it on)
+p_sent_to_mastodon() { podman exec pasture-mongo mongosh --quiet PrivaPub --eval "print(db.Job.find({Kind: 0, CreatedAt: {\$gt: new Date(Date.now() - 600000)}}).toArray().filter(j => j.Payload.includes('\"Inbox\":\"https://mastodon.test') && j.Payload.includes('$1')).length)"; }
+[ "$(p_sent_to_mastodon "$reply_uri")" = "0" ] && ok "carol's reply is not delivered there" || ko "PrivaPub delivered carol's reply to Mastodon unasked"
 
 m_rails "Status.find_by(uri: \"$root_uri\").update_columns(created_at: 10.minutes.ago, fetched_replies_at: nil)" >/dev/null
 root_on_m=$(m_rails "puts Status.find_by(uri: \"$root_uri\").id")