How to Deploy Magento 2 on Cloudways

In this guide, you will learn how to install the latest Magento 2.4.x on your Cloudways server in just a few clicks.

Emmad avatar
Written by Emmad
Updated this week

Table of Contents

Cloudways Managed Hosting is a one-window solution to power up your Magento store and is trusted by thousands of eCommerce businesses and agencies. The Cloudways blazing-fast stack delivers faster performance, ironclad security, scalability with a choice of five cloud providers, and guaranteed peace of mind with 24/7/365 support.

In this guide, you will learn how to install the latest Magento 2.4.x on your Cloudways server in just a few clicks.

Magento 2.4.x Minimum Requirements

When you launch a Magento 2.4.x application on a new server, all the required settings and packages are configured automatically. However, if you want to deploy the Magento application on an existing server, it should meet the following minimum requirements.

Tip

  • You can still install Magento 2.4.x on a 4GB RAM machine; however, you may face performance-related issues.

  • The PHP memory and execution limits are based on an 8GB machine. You need to increase proportionally for bigger machines.

How to Deploy Magento 2 on Cloudways

You can deploy Magento 2.4.x on a new server or an existing server, and we have explained the procedure below:

Prerequisites

To reiterate, when you launch a Magento 2.4.x application on a new server, all the required settings and packages are configured automatically. However, it should meet the minimum requirements if you want to deploy the Magento application on an existing server.

Launching Magento 2 on an Existing Server

Log in to the Cloudways Platform using your preferred method.

  1. From the top menu bar, click Servers.

  2. Then, choose your target server where you wish to deploy your Magento 2 application.

  3. Click to view more options.

  4. Then, click Add Application.

  5. Next, select Magento 2.4.x.

  6. Name your Application.

  7. Select your Project.

  8. Finally, click Add Application.

Important

If your existing server cannot meet the minimum requirements to run Magento 2.4.x, then you will be informed here, as shown in this image. All the recommended server packages and services will be installed and configured automatically if you deploy your application.

Your high-speed Magento application will be deployed in a few minutes. Learn how to access your application information, such as your application URL, admin credentials, etc.

Launching Magento 2 on a New Server

Log in to the Cloudways Platform using your preferred method.

  1. From the top menu bar, click Servers.

  2. Then, click Add Server.

  3. Select Magento 2.4.x.

  4. Type the name of your application.

  5. Type the name of your server.

  6. Select your Project.

  7. Choose your cloud provider.

  8. Select the server size.

  9. Choose the server location.

  10. Finally, click Launch Now.

Your high-speed Magento application will be deployed in a few minutes. Learn how to access your application information, such as your application URL, admin credentials, etc.

Important Notes

  1. You may see a bit of delay when viewing the frontend and backend for the first time because it compiles all the assets like JS and CSS files, core functions, etc.

  2. You also don’t need to configure Varnish settings to make your application work. All the default exclusions are already excluded by default.

  3. Varnish purge does not work with Magento 2; however, you can purge the Varnish cache directly from the Cloudways Platform.

That’s it! We hope this article was helpful. If you need any help, then feel free to search your query on Cloudways Support Center or contact us via chat (Need a Hand > Send us a Message). Alternatively, you can also create a support ticket.

FAQs

I cannot clone my Magento 2.x application to an existing server. What’s going on?

Please ensure that you are cloning your application on a compliant server with all the required packages to run. You might need to scale up your server or update your server packages.

Did this answer your question?