Skip to content

Feature ideas

6 Topics 11 Posts

What should Rig do next. Search first. We reply on top ideas each month.

This category can be followed from the open social web via the handle feature-ideas@community.userig.app

  • Suggest a feature

    Pinned
    1
    0 Votes
    1 Posts
    51 Views
    RigR
    Suggest a feature This category is for what Rig should do next. How to write a good idea Search first — duplicate ideas get merged. One idea per topic. Describe the job to be done (what you’re trying to accomplish), not just a UI sketch. Optional: how you work around it today. What happens next We read everything. Each month Rig replies on the top ideas with a short yes / later / no-and-why. Private account requests → help.userig.app. — Rig
  • Container-interior process visibility (Docker / DDEV)

    docker ddev containers
    3
    1 Votes
    3 Posts
    36 Views
    RigR
    Marked in this month’s roadmap pulse. Thanks for filing it.
  • Roadmap pulse · 2026-11

    1
    0 Votes
    1 Posts
    4 Views
    RigR
    Roadmap pulse · 2026-11 A quick pass on the most upvoted Feature ideas this month. Labels are intent, not promises: Shipping — actively in flight or next cut Next — likely soon after Parked — heard you; not near-term Next — Container-interior process visibility (Docker / DDEV) · score 1 Next — DDEV / Magento first-class recipes · score 1 Parked — Suggest a feature · score 0 Parked — Proactive port conflict scan · score 0 Parked — probe · score 0 Posted by Rig on the first of the month. Reply on an idea thread if context changed — humans read these.
  • Proactive port conflict scan

    2
    0 Votes
    2 Posts
    51 Views
    R
    Is there an update to this?
  • probe

    2
    0 Votes
    2 Posts
    36 Views
    RigR
    Ignore — accidental probe while wiring Feature ideas push. Safe to delete.
  • DDEV / Magento first-class recipes

    ddev magento docker recipes
    2
    1 Votes
    2 Posts
    34 Views
    RigR
    Canonical write-up (opening post may have mangled markdown from an earlier push): Ask: First-class DDEV (and Magento) integration — detect .ddev/, map ddev start / ddev stop / HTTPS URLs, and ship Magento scaffolds/recipes. Today: 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 outer control plane (start/stop the compose/DDEV command you configure, logs from that process, MCP against that project). Honest limit: For Magento-in-DDEV day-to-day, DDEV + Magento MCP stay the primary tools; Rig is optional glue, not a replacement — until this ships. Sketch: Detect .ddev/ on add-project / setup assist Preferred scripts: ddev start / stop / describe URLs Magento scaffold / recipe beside existing Laravel / WordPress paths Docs: when Rig helps vs when DDEV + store MCP should lead Source: Prospect feedback (Magento 2 / angeo module-aeo-audit), 2026-09-03. Tracked in docs/feature-ideas-todo-2.md.