What order to upgrade from 2.3.5-P1 to 2.4

[andrewadco53d9]

Hi All, 

My current set up is on Cloudways is:

PHP - 7.3

MariaDB 10.1

Elastic Search - Not installed 

Magento 2.3.5-P1

I have 2 Applications set up on my server. One is a live webshop, the other is a staging application (direct copy of the live webshop)

I want to upgrade the staging server to Magento 2.4 first, check everything works and then upgrade the live application. 

Question 1 

If I upgrade the Server to PHP 7.4, MariaBD 10.4 and turn on ElasticSearch 7.6.

Will it affect my live application running 2.3.5-P1  (are these all compatible with M 2.3.5-P1 ?)

Question 2

What order should I upgrade them? 

[gaurav_harsh1]

Hello @andrewadco53d9 

You can create a new testing instance on Cloudways and pull everything from live to there.

and Cloudway supports to enhance each instance/application with different PHP version, you can approaches in the server configurations, read out this article to understand how to manage different php and Maria DB version on particular application :

https://support.cloudways.com/how-to-manage-server-settings/

So answer of Q1 :

NO, Magento 2.3.5 may have some modules which doesn't support php or MariaDB upgraded versions.

Q2 :

First create a copy of live to another instance or pull it on local with expected configurations,

then upgrade the magento version and check all the possible pages and scenarios and then push everything to staging with correct configurations and a complete check and later push everything to live folder.

[andrewadco53d9]

@gaurav_harsh1 Thankyou for your reply. Very helpful. 

Using the  Cloudways platform you can only set PHP and MySQL by server, not by application,

Are you suggesting I clone the current server to a new server, upgrade the new server, and then copy the data back to the original live server? 

[gaurav_harsh1]

@andrewadco53d9 

I just checked here that we can set php version per application :

https://support.cloudways.com/how-to-manage-server-settings/

and yes, clone your running project to a different server, configure that server and upgrade Magento version.

and if it looks fine to you, pull data to the live server and change the configurations of php mariadb and Elasticsearch.

[Pistle1992da70]

Note: please check php7.4 version and elasticsearch installed.

First take to older version website backup and after your run direct magento 2.4.0 version.

Magento Open Source:

composer require magento/product-community-edition=2.4.0 --no-update

Magento Commerce:

composer require magento/product-enterprise-edition=2.4.0 --no-update

UPDATE:-

I will explain more in how to update latest magento version (2.4 at the moment):.

composer require magento/product-community-edition=2.4.0 --no-update

composer update

If you are running Magento 2 commerce the command will be slightly different:

composer require magento/product-enterprise-edition=2.4.0 --no-update

composer update

Replace 2.4 with the latest M2 version.

When it is completed, run another SSH command and upgrade the Magento database:

php bin/magento setup:upgrade

After that you will want to recompile if you are in production mode:

php bin/magento deploy:mode:set production

You’ve successfully performed a Magento 2 upgrade! Now go to the frontend and backend and check everything.