- Composer Path Repositories
- Shopware’s psh.phar Command Line Tool
- Shopware: Code that’s theirs, Code that’s yours
- Composer vs. History
- Wrap Up on “Shopware’s Development Environment”
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.