I’m sure you’ll agree that Magento is a very resource heavy software and requires a stable setup to run it smoothly. We’ve all been in a situation where we’ve complained how slow the Magento system is to run locally but what if I told you there is a docker setup for Magento which is ready to use and only requires one command to have your environment ready? Yes only command!
In my early days as a Magento developer, I’d marry with a fact that we should never rely on a local WAMP/XAMP setup to run Magento and I was introduced to Docker but that being said, there were so many Magento instances to choose from. Some required custom integrations/plugins and some were not good enough to use.
I then stumbled upon a ready-to-use Docker cloundpanel instance which was purely focused on providing developers with a stable Magento development setup in one step, and the step was to install the Docker image locally and viola you have a cloudpanel quite similar to CPanel which allows us to create/list multiple development domains and it was packaged with Elasticsearch, MySQL and Varnish to support Magento.
The Docker instance I’m referring to is create by MGT-Commerce which is a Magento cloud hosting providers. I’ve detailed the steps below to install and setup a Magento development domain.
The MGT Docker image comes in all stable version of PHP starting from PHP 7.0 up to PHP 7.4. You can pick and choose the PHP image you need and even you can run multiple instances at the same time (just ensure each instance has a unique port).
Since Magento 2.4 is now our and ready to use so let’s setup a PHP 7.3 instance and install Magento.
First, we need to install the PHP 7.4 image and to do that, run the following command in your Docker CLI.
Finally, simply download the Magento 2.4 composer file or the whole package from their GIT repo and upload to the directory specified above. Once done, connect to the server using SSH and you can safe run the Magento installation commands to install Magento.
That’s all! No rocket science!
Do you have any questions or feedback? Please let me know in the comments!
Recently, one of our clients started to get $.widget is not a function JS error on their Magento 2 store and as a result, customers weren’t able to complete their checkout.
The error was present on Minicart, Product view page, and Checkout page and even changing to default Magento 2 template did not fix the issue. Eventually, I found that the issue was with Magento JS merging and I was able to fix the issue by making the following changes:
I’ve used Magento v2.1.x for a while and then decided to give Magento v2.2.2 a try because why not, upgrading the tech stack is always good, isn’t it?
As usual, I opted in for CLI based installation and Magento was installed successfully, however, I was served a 500 Internal Server Error whenever I tried to access the website.
I’ve learnt from my experience is this error usually occurs when something is wrong with .htaccess file and that’s where I looked for this fix as well.
I removed .htaccess file and the site was back online, however, it still didn’t work properly. I then added the .htaccess file back and the error came up again.
I also looked at the server error log but there wasn’t much information available. Eventually, I decided to play around with apache modules and noticed that mod_version was disabled. I activated mod_version, restarted apache service and hello world, the site was back online.
So in a nutshell:
Check webserver modules – in my case, the problem was with mod_version as it was disabled. Enabling it fixed the issue.
Enable/Disable your htaccess file to see if it resolves your issue
Disable third-party extensions one by one to troubleshoot
If the issue persists, visit the Magento community forums and post your issue there.
Magento is a complex system and it is important to pay close attention to what you code.
One of my clients had a special requirement in which I had to customise the customer login controller to meet the business needs.
One option was to create a custom controller and add a preference in di.xml, and the other option was to write a Magento Plugin. I opted in for the later option.
Everything worked fine on my local and the plugin worked as expected but when it was deployed on the test server, it did not work and returned the following error:
Plugin class Vendor\ModuleName\Plugin doesn't exist
I tried Google, StackOverFlow, Magento community forums and every single website but did not find a solution at all. Eventually, I decided to reiterate the local installation steps to the test server and noticed that on my local I hadn’t used Composer to deploy the package whereas on the test server, the package was deployed using composer.
It was good head start and then I knew the issue is with composer file. After reviewing the file, I found out that everything in the file was fine except the missing PSR-4 element.
I am one of the first ones to become Magento 2 Certified Solution Specialist and I am also a Magento v1 Certified Solution Specialist. I work as a Lead Magento Developer at a Magento Agency based in Luton, Bedfordshire.
I love Magento and love helping other Magento developers & retailers. You can follow me on Twitter or get in touch via the form at the bottom of this page.