<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Wordpress on 5glinux</title><link>https://blog.5glinux.com/tags/wordpress/</link><description>Recent content in Wordpress on 5glinux</description><image><title>5glinux</title><url>https://blog.5glinux.com/images/og-default.jpg</url><link>https://blog.5glinux.com/images/og-default.jpg</link></image><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 03 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.5glinux.com/tags/wordpress/index.xml" rel="self" type="application/rss+xml"/><item><title>Replacing Aria Orchestrator, Part 3: forms, schedules, approved content and workflows with SUSE Multi-Linux Manager</title><link>https://blog.5glinux.com/posts/replacing-aria-orchestrator-part-3-day-2-suse-multi-linux-manager/</link><pubDate>Tue, 03 Nov 2026 00:00:00 +0000</pubDate><guid>https://blog.5glinux.com/posts/replacing-aria-orchestrator-part-3-day-2-suse-multi-linux-manager/</guid><description>Part 3 of replacing Aria Orchestrator: four day-2 patterns that Aria users rely on, rebuilt in SUSE Multi-Linux Manager. A Salt formula with a web form, a recurring highstate on a system group, dev and prod content snapshots, and an action chain that upgrades an outdated package, reapplies the state and runs a smoke test.</description></item><item><title>Replacing Aria Orchestrator, Part 2: reusing Salt states with SUSE Multi-Linux Manager</title><link>https://blog.5glinux.com/posts/replacing-aria-orchestrator-part-2-salt-suse-multi-linux-manager/</link><pubDate>Mon, 02 Nov 2026 22:00:00 +0000</pubDate><guid>https://blog.5glinux.com/posts/replacing-aria-orchestrator-part-2-salt-suse-multi-linux-manager/</guid><description>Part 2 of replacing Aria Orchestrator: the Salt state an Aria cloud template applies runs unchanged from SUSE Multi-Linux Manager. A VM bootstraps itself with cloud-init on SUSE Virtualization, registers with an activation key, gets WordPress from a highstate, and is then changed and kept in line from SUSE Multi-Linux Manager.</description></item></channel></rss>