For “barely any modules” I will assume that is around 3 modules. you’ll need to audit those modules and update all of them to new versions, while also stepping Magento through the major versions. 2.2.7 is a very old version so you should step it up to 2.3.0, then 2.3.1, 2.3.2, etc. I don’t like skipping versions when upgrading as there could be issues with the upgrade, and it could be hard to detect which version is causing the issue (and why). You should also test all functionality of the site along with all modules in each step up. Very time consuming!! And if the site is running a third-party theme, I wouldn’t even attempt it without removing that theme first. You could of course jump straight from 2.2.7 to 2.4.7, but this rarely works well and will most likely fail. Note that you have package and system dependencies that could also change with every version. My ballpark is “months” 😄

Thanks so much Nishan! 🥰

Thanks! I generally recommend a managed hosting solution at this time, as simply figuring out how to deploy Magento is super time consuming (I’d rather stick with writing code). It is a problem that I’m thinking about. That said, I’d recommend looking up Damien’s Kubernetes setups to learn how to run a proper containerization setup for Magento.

@@MarkShust Thanks for the response Mark! Do you know of anyone who has successfully deployed your Docker-Magento solution to a host? It is working fine on my machine. But I want to deploy it to a host and make it publicly available as an actual store for my daughter.

@@pslamba I don't, but feel free to try it out!

Hi there - thanks for the kind words! This environment is meant for development, so some updates would need to be made for prod, including customizing the images and such. I don’t have a formal process for this and generally leave it up to each use-case to implement at the moment, though I am thinking through deployment options.

Tried to make it very entry-level. Sometimes it’s good to brush up on the basics 😎

Glad you found it useful! 👍

Changes to packages and etc. should always flow through code. So the process for this would be to commit the composer json/lock files through VCS. if you don’t do this, you create an inconsistent environment state.

@@MarkShust thank so much

One more question, according to your extensive experience, which method is best to generate local Magento cloud environments, with docker or raw files, that is, exporting the database from the cloud to the local environment and files, etc. Do you know any tools to produce a local Magento cloud environment, any tutorial? Thank you very much for sharing your knowledge, best regards 😃

@@aurelioflores4571 I just use docker-magento for everything -- even Adobe Commerce Cloud projects. I don't often need to pull down a database, but when I do, I have a simple bash script which imports it to a local database and then updates the related config values to get it to run locally (base_url, etc.).

@@MarkShust thank you so much, do you know any concise docker-magento tutorial (or videotutorial)

I use PhpStorm, and have been doing so for many years. Highly recommend it 👍

If a company can’t see the ROI from investing in superior dev talent, you probably don’t want to work for that company anyways.

I think it’s important for developers to mention their accomplishments and passions. Some companies have a hard time bringing up these topics, but if you can it will help to set you apart from other candidates.

It sounds like your installation failed, as that should work out of the box. I’d recommend opening up a new discussion thread on GitHub about this.

Thanks Suraj 🙏

For the most part - they are the same core codebase.

It’s no different from creating a custom log file in a non-docker-magento project.

Suggest me any genuine link to set custom log file which can definitely works with magento setups with docker using your m2 docker

@@MarkShust Suggest me any genuine link to set custom log file which can definitely works with magento setups with docker using your m2 docker

Flows off the tongue better 😛

Thanks Enrique - glad you liked it 😎

🙌

I use an M1 MBP Max with 64GB RAM and a 4TB SSD (which does speed up I/O a bit) - it’s the first computer in the last decade that I’ve loved, and it performs insanely well. You may be able to get similar performance with a newer MBA though with maxed out RAM. The new M computers are so fast.

Sure thing Ahmed, glad you liked it 👍

You got it Benjamin 🤓

Thanks Haroon! 🙌

You're welcome, yes if you have any requests for new ones, lmk!

Really appreciate it Volodya 🙏

As soon as the official versions are tagged! Still waiting for them to drop from Adobe 😅

@@MarkShust Have been tagged some minutes after your comment :)

Thanks so much Finn! 😄

You're welcome! 😇

​@@MarkShust Do you or are you planning and course for PWA with magento on Macadamy?

​@@KaFFi3N I don't have plans to create a PWA Studio course -- AFAIK, that project is dead (though it's my most requested topic). You can see the contribution charts for yourself at github.com/magento/pwa-studio/graphs/code-frequency -- though there were some pushes lately, of all the devs that have worked with PWA Studio, none of them mentioned that they actually liked working on it, which I believe is an important factor. It's possible that I'll cover PWA-related material through another headless solution that has more traction and higher developer happiness, such as Vue Storefront.

Sorry to hear that!

Yup Magento stands alone 🫡

You'll probably still need a module that logs the output.

Adobe Commerce or Magento OS, you should always commit both the composer.json and composer.lock files. Composer.json keeps track of the package versions, and the lock file "pegs" to an exact installed package/version, which ensures consistency between environments.

@@MarkShust thank so much, Sr.

Feel free to create a new Discussion on GitHub and myself or someone else will help you resolve your issue 😊

I’ve been coding in vi/vim for 15+ years and still have no clue what the difference is.

@@MarkShust vim = vi improved. vim has syntax highlighting as a feature you can enable. some distros automatically symlink vi to vim

You’re welcome Lukas, so glad you enjoyed it!! 🎉

Thank you, I’m so happy to hear that! 😁

Yes, you can change the ports in compose.yaml (host:container) and update the site’s base URL.

@@MarkShust thank you.

Sorry, I don't as I've been out of Magento contracting/consulting work for some time. Good luck!

@@MarkShust many thanks for the reply, keep in touch, have a good weekend!

This was strictly an presentation about exploring AI for Magento development. It's also already drastically improved since I gave this speech at MMFL.

So glad it was helpful! I'll do my best to create more videos like this.