Recent Posts


Wrap Up on “Shopware’s Development Environment”


Frustrated by Magento? Then you’ll love Commerce Bug, the must have debugging extension for anyone using Magento. Whether you’re just starting out or you’re a seasoned pro, Commerce Bug will save you and your team hours everyday. Grab a copy and start working with Magento instead of against it.

Updated for Magento 2! No Frills Magento Layout is the only Magento front end book you'll ever need. Get your copy today!

This entry is part 5 of 5 in the series Shopware's Development Environment. Earlier posts include Composer Path Repositories, Shopware's psh.phar Command Line Tool, Shopware: Code that's theirs, Code that's yours, and Composer vs. History. This is the most recent post in the series.

I didn’t intend to write a four article series on Shopware — I just wanted to do a small follow-up to something I wrote here

Learning the differences between shopware/platform, shopware/development, and shopware/production is probably required if you’re going to get serious about Shopware development

and discovered that my “finding the most technically contradictory part of a platform” sixth sense is still alive and well. I would have liked to dive deeper on some of those path repositories, the shopware extension store, the unofficial friends of shopware composer repository and, more generally, what look like big changes in Shopware 5 vs Shopware 6 — but a hobbyist only has so much time.

It seems like Shopware is mid-transition on a lot of this. If you’re going to adopt the platform be ready for more changes here. Also, it sounds like Shopware holds regular community events called “Boost Days”, and the next one is going to have workshops on both docker and composer where you might be able to clarify a lot of the ambiguity around what Shopware’s intentions are around how you use all this tech.

Series Navigation<< Composer vs. History

Copyright © Alan Storm 1975 – 2022 All Rights Reserved

Originally Posted: 22nd May 2021