WooCommerce and Magento proudly stand as two of the most popular e-commerce solutions that power jointly nearly 40% of all e-stores on the web. While both have their strengths and weaknesses, it becomes quite challenging for a merchant to choose the best one amongst the two.
This article is aimed to help you give the answer to an ultimate question: What’s better for your business?
This could sound weird, but should be strong as think global, act local: work on remote server, locally.
Many programmers are using Mac, while some other developers are taking advantages of Linux latest technologies (such as Docker). Other people are just so old school, they still using the Microsoft and we have to respect that, if that works (and it should actually).
This year I was excited and honoured to have a workshop at Meet Magento 2017 Romania on October 17th.
From the arrival, the venue Grand Hotel Italia was great and we were very warm welcome, especially after a longer flight time because of the weather conditions (more precisely the airport was closed due to an intense fog and the airplane had to make circles in the air for about one hour).
The organisers did a really great job and they switched my speech. Ben Marks cooled me down with a bottle of water, which proved more than useful for my emotions which I usually have when I present in public.
Nordic Web Team organised Meet Magento 2017 Sweden for the second time, in Stockholm. The event toked place in Münchenbryggeriet (or the “Brewery Conference Center”).
After being in the panel moderator a year ago, this time I had the pleasure to talk on my first public presentation, which Nexcess described it being “a particularly interesting talk about Kubernetes and Magento 2".
Migrating from Magento 1.x to Magento 2.x can be seen as a long and complex process, especially when having many custom extensions. It involves the data, the extensions, the themes and all the customisations.
To avoid additional issues is recommended to start first with the migration on a fresh Magento 2.x installation (using DevBox), which will bring all the settings, products, categories, cms pages, blocks, orders, url rewrites and customers. If it starts with the design, the changes (pages and settings) will be overwritten by the official data migration tool and might cost some time to add them back. Changes made during theme design might enter in conflict with the migration tool (for example creating new attributes, which will be time consuming to debug).
With some experience on docker-compose, Kubernetes seems very stable, quick and reliable solution for the need of pushing a Magento 2.x project into the cloud.
There are also alternatives such as docker swarm (which has a more gengle learning curve when having docker-compose background). Willing to test multiple solutions, Kubernetes does not disappoint when doing the translation from local project into the cloud.
A new simplified way of adding a question and getting answers. First project will be launch only in romanian and will be build with #RoR, will have facebook authentification, #elasticsearch autocomplete, #bootstrap responsive theme.
To access a docker application by a particular hostname, the file: /var/lib/docker/containers/CONTAINER_ID/config.json requires the change of the Hostname and Domainname "Config":{"Hostname":"www","Domainname":"example.local", ...}. This way, the container will have all the necesarry information.
