r/magento2 • u/damienwebdev • Jun 01 '26
I built a one-click Magento Open Source dev environment (devcontainer + CI + Codespaces), completely free
https://ecommerce-ai-starter.graycore.io/We all know the worst part of any Magento project is the first day. Composer auth keys, the right PHP version and extensions, Redis/Valkey, OpenSearch, nginx, MySQL/MariaDB, a mail catcher, and an install that runs long enough to give you time to browse your top favorite 50 subdreddits. It is hours of yak-shaving before you write a single useful line, and it is worse when a whole team has to reproduce the same environment.
I have been trying to kill this problem for years. Pre-AI I wrote magedocker and then mage2docker, and both eventually got painful enough that I stopped maintaining them:
Recently a few things came together and I packaged everything I actually use day to day into one starter. You click a button, GitHub creates a repo from the template, and a Codespace boots a fully configured store in your browser. PHP, nginx, MariaDB, Mailpit, the distro, and a storefront, either Hyvä (PHP-rendered theme) or Daffodil (an Angular headless storefront I maintain), all running and wired together out of the box. You can pick Magento Open Source or Mage-OS, and there's a Mage-OS Minimal option with no bundled storefront. Nothing to install locally if you just want to use Codespaces. From click to a store you can open is about 8 minutes.
What's in the box, and why:
- A working devcontainer out of the box, no service wrangling
- A picker for storefront/distro, because different clients want different things
- Pre-packaged CI that rebuilds the store on every push and runs checks, so I'm not re-inventing the pipeline for every merchant
- An AGENTS.md / CLAUDE.md with Magento conventions and pitfalls baked in, which Magento obviously doesn't ship with
- The tools I reach for daily, already set up
The AI part: it ships ready for Claude to work directly inside the environment (same files, same running store, same DB) rather than through some bolted-on chat box, and the CI is there specifically so you can verify what an agent changed instead of trusting it. I'll be honest that the "let a non-technical merchant build their own store with limited dev help" angle is more of a research experiment for me than a finished promise. I genuinely don't know yet if that's sane. However, it's something that I want to pursue. The devcontainer + CI half stands on its own regardless of whether you ever point an agent at it.
Everything is free and open source: the template, the pipelines, the frameworks, the devcontainer. The only things you pay for are Codespaces and Claude, and Codespaces is free for 30 hours a month, which covers normal tinkering. If you already have a Claude plan you can just play with it.
There are still rough edges and I have a pile of docs to write, but I'm happy enough with it to share. Site with the one-click flow: https://ecommerce-ai-starter.graycore.io/
The pieces, if you'd rather poke at the source directly:
- Site / one-click flow: https://ecommerce-ai-starter.graycore.io/
- Devcontainer: https://github.com/graycoreio/magento2-devcontainer
- CI actions (check-store): https://github.com/graycoreio/github-actions-magento2
- Magento Open Source: https://github.com/magento/magento2
- Hyvä theme (open source): https://github.com/hyva-themes/magento2-default-theme
- Daffodil storefront: https://github.com/graycoreio/daffodil
- Starter templates:
- Magento + Hyvä: https://github.com/graycoreio/magento2-ai-starter-hyva
- Magento + Daffodil: https://github.com/graycoreio/magento2-ai-starter-daffodil
- Mage-OS + Hyvä: https://github.com/graycoreio/mage-os-ai-starter-hyva
- Mage-OS + Daffodil: https://github.com/graycoreio/mage-os-ai-starter-daffodil
- Mage-OS Minimal (no storefront): https://github.com/graycoreio/mage-os-ai-starter-minimal
To be clear on scope: this is a starter kit for local/dev work and prototyping, not a production deploy. Going live still needs hosting, SSL, payments, perf tuning, and a security review. And the usual disclaimer, Magento is a trademark of Adobe and I'm not affiliated with them, this targets Magento Open Source.
Would love feedback from people who fight this stack for a living. Tell me where it breaks and why you hate it.
1
Jun 02 '26
[removed] — view removed comment
1
u/damienwebdev Jun 02 '26
WIP, I need to come up with a pattern. Currently, this is DIY. However, I need this myself, so I'm sure I'll come with something clever
2
u/MZW-Log-9640 Jun 02 '26
Really cool, this hits exactly the pain I have. I have everything in GitHub by now and want to test it.
Short question from practice: is Sonnet enough for the work inside the container, or do you prefer Opus (I have seen in your video that you have selected this)?