Im neuesten Blog-„Fight“ zwischen Roman Zenner, Alexander Ringsdorff und Andi Unger geht es sehr stark darum, inwieweit Shopsystem-Hersteller Innovationstreiber sein können (zB Magento, OXID, Shopware oder andere) und wie Händler innovativ sein müssen. Als langjähriger Beobachter der Szene aus technologischer Sicht habe ich dazu meine eigene Meinung, die ich unter der Überschrift E-Commerce Brainfucks mal subsummieren möchte. Im Kern geht es dabei um die Frage: Was braucht es, damit Online-Händler auch zukünftig noch im E-Commerce bestehen können? Und wie innovativ müssen die Plattformen sein, auf die die Hersteller setzen? Wie müssen sich Händler ändern?
Developers in smaller and larger e-commerce agencies/shops are often faced with different development environments. Customers who want to evaluate e-commerce platforms like Magento, OXID or Shopware have to handle everything from downloading the packages, their LAMP stack and installing it on-the-go. Of course, you might have your own virtual machine, but for a quick shot you have to create another virtual host etc.
But there’s a solution for that: a vagrant/puppet based development environment for Magento, OXID and Shopware. It consists of a Vagrant build and uses standard puppet recipes for Apache, PHP etc, as well as own (open source) recipes for Magento, OXID and Shopware and installs the appropriate shop system in a box together with a lot of PHP tools.
All you have to do is clone the commerce-dev-environment repository from GitHub and vagrant up :-)
Feature enhancements and Pull Requests are welcome.
[You may have heard about the Magento fork Mage+.]
Lee, just tell us: who are you and what are you doing?
I’m a Magento technical architect, developer and contributor to Magento CE. I specialise in architecting and building large scale and complex installations of Magento – having built enterprise Magento platforms for Warner Music Group both in Europe & USA, and for Rebate Networks, who operate a collection of localised flash-sales websites throughout the world. I’m also the founder of the London Magento Users Group.
I created a fork of Magento CE called Mage+, after the frustrations I’d experienced whilst working with Magento.
Yesterday, it was the news of the day: Magento CE 1.7 was forked on GitHub by some community people. After the spectacular departure of Yoav Kutner, then-CTO at Magento (TechCrunch reported), it was just a matter of time until Magento was forked. Indeed, as Vinai Kopp pointed out on twitter, there have been some forks of Magento already (project agent-ohm, a fork of Magento 1.3), but Mage+ seems to be another case.
What are the reasons of the fork of Magento? And what’s in it for the Magento community?
Die Nachricht des Tages: Magento CE 1.7 wurde auf GitHub von der Community geforkt. Nach dem spektakulären Weggang von Yoav Kutner, CTO bei Magento (ExcitingCommerce und TechCrunch berichteten), war es wohl nur eine Frage der Zeit, bis Magento geforkt wurde.
Was sind die Gründe des Forks von Magento? Und was kann dieser Schritt für die Community bedeuten?
E-commerce teams within IT departments must do more with less, so they need to maximize their resources through shrewd and clever management, according to Gartner.
In the last weeks, MAYFLOWER – Germany’s biggest PHP solution provider for business critical web applications – re-evaluated its preferred shop supplier for eShop projects. As you may remember, we are a premium solution partner for OXID eSales, but also have deeper experience with xt:commerce and self-made shops (German case study) for our eShop projects. Recently, we had a deeper look at Magento which seems to be like a „rising star“ on the PHP-based eShop systems and looked if it could be an alternative for enterprise projects (as we concentrate on the bigger B2B and B2C enterprise business).
Right after this re-evaluation (which was not very good for Magento, btw) I created some presentation slides and held a session at the German E-Commerce Conference 2009 roadshow in German. Today I translated the slides (which were widely mentioned at the Exciting Commerce Blog in German and English, at the German Shopanbieter Blog, at the Blog of a Magento Partner Visions Media and at the Blog of the German T3N magazine). Below you find the English slides (which were also slightly updated) from slideshare. German speaking readers can go directly to the German slides on slideshare.