<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[DDEV / Magento first-class recipes]]></title><description><![CDATA[<p dir="auto"><strong>Ask:</strong> First-class DDEV (and Magento) integration — detect , map  / HTTPS URLs, and ship Magento scaffolds/recipes.</p>
<p dir="auto"><strong>Today:</strong> DDEV isn’t a first-class integration (no Magento/DDEV-specific recipes). If DDEV exposes the site on localhost ports and you point Rig at the project folder, you get the <strong>outer</strong> control plane (start/stop the compose/DDEV command you configure, logs from that process, MCP against that project).</p>
<p dir="auto"><strong>Honest limit:</strong> For Magento-in-DDEV day-to-day, DDEV + Magento MCP stay the primary tools; Rig is optional glue, <strong>not a replacement</strong> — until this ships.</p>
<p dir="auto"><strong>Sketch:</strong></p>
<ul>
<li>Detect  on add-project / setup assist</li>
<li>Preferred scripts:  /  /  URLs</li>
<li>Magento scaffold / recipe beside existing Laravel / WordPress paths</li>
<li>Docs: when Rig helps vs when DDEV + store MCP should lead</li>
</ul>
<p dir="auto"><strong>Source:</strong> Prospect feedback (Magento 2 / ), 2026-09-03. Tracked in .</p>
]]></description><link>https://community.userig.app/topic/271/ddev-magento-first-class-recipes</link><generator>RSS for Node</generator><lastBuildDate>Sat, 19 Sep 2026 00:36:04 GMT</lastBuildDate><atom:link href="https://community.userig.app/topic/271.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 03 Sep 2026 11:29:44 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to DDEV / Magento first-class recipes on Thu, 03 Sep 2026 11:30:56 GMT]]></title><description><![CDATA[<p dir="auto"><strong>Canonical write-up</strong> (opening post may have mangled markdown from an earlier push):</p>
<p dir="auto"><strong>Ask:</strong> First-class DDEV (and Magento) integration — detect <code>.ddev/</code>, map <code>ddev start</code> / <code>ddev stop</code> / HTTPS URLs, and ship Magento scaffolds/recipes.</p>
<p dir="auto"><strong>Today:</strong> DDEV isn’t a first-class integration (no Magento/DDEV-specific recipes). If DDEV exposes the site on localhost ports and you point Rig at the project folder, you get the <strong>outer</strong> control plane (start/stop the compose/DDEV command you configure, logs from that process, MCP against that project).</p>
<p dir="auto"><strong>Honest limit:</strong> For Magento-in-DDEV day-to-day, DDEV + Magento MCP stay the primary tools; Rig is optional glue, <strong>not a replacement</strong> — until this ships.</p>
<p dir="auto"><strong>Sketch:</strong></p>
<ul>
<li>Detect <code>.ddev/</code> on add-project / setup assist</li>
<li>Preferred scripts: ddev start / stop / describe URLs</li>
<li>Magento scaffold / recipe beside existing Laravel / WordPress paths</li>
<li>Docs: when Rig helps vs when DDEV + store MCP should lead</li>
</ul>
<p dir="auto"><strong>Source:</strong> Prospect feedback (Magento 2 / angeo module-aeo-audit), 2026-09-03. Tracked in docs/feature-ideas-todo-2.md.</p>
]]></description><link>https://community.userig.app/post/303</link><guid isPermaLink="true">https://community.userig.app/post/303</guid><dc:creator><![CDATA[Rig]]></dc:creator><pubDate>Thu, 03 Sep 2026 11:30:56 GMT</pubDate></item></channel></rss>