Increase disk space for Integration environment on Cloud

To increase the persistent disk space for your Integration environment, specify the required space in the disk key of the magento.app.yaml configuration file, then Git push the file to the environment (see detailed steps).

To allocate more disk space for a service (MySQL, Redis, Elasticsearch and others), specify the required space in the disk key of the .magento/service.yaml config file, then Git push to the environment (see detailed steps).

We recommend to start reading from the explanation on how the disk space allocation is configured on Integration (see the section below); however, you may jump straight to the detailed steps.

Related Knowledge Base article: Check disk space on Cloud environment using CLI.

Theory: how disk space allocation is configured

The disk space on the Integration environment of a Cloud project is configured using these two YAML files:

• .magento.app.yaml
• .magento/service.yaml

magento.app.yaml

.magento.app.yaml (the disk key) sets the persistent disk space reserved for your entire application on the Integration environment. The default disk space is 2GB (2048MB).

Below is the example of the disk key of the .magento.app.yaml file:

# The size of the persistent disk of the application (in MB).
        disk: 2048

See also in this article: Increase disk space allocation for your application on Integration environment.

Related documentation on DevDocs: Configure application on an environment.

.magento/service.yaml

.magento/service.yaml (the disk key) sets the disk space for services used by your application. These services include MySQL, Redis, ElasticSearch (for Magento Cloud 2.1.x and later) and others.

As a default, only the MySQL service is included in the .magento/service.yaml file:

mysql:
        type: mysql:10.0
        disk: 2048

See also in this article: Add services and allocate disk space for them.

Related documentation on DevDocs: Configure services on an environment.

How total disk space for Integration environment is calculated

The total disk space capacity must be mentioned in your Magento Commerce (Cloud) agreement. To check the capacity in your Project Web Interface, go to https://accounts.magento.cloud/user and check the Storage parameter: it shows the disk space you may use for every Integration environment you have in your Cloud project.

For example, if you have three Integration environments (two of which have been branched from the main Integration environment) and the Storage parameter is 5GB, the disk space capacity for each of your Integration environments is 5GB.

The disk space allocation for any of your Integration environments is calculated as the sum of values in the disk keys of the .magento.app.yaml and the .magento/services.yaml files, and must not exceed the Storage parameter in your Project Web Interface.

To see your actual disk space utilization, you may check disk space on Cloud environment using CLI.

Increase disk space allocation for your application on Integration environment

To change (increase or decrease) the disk space, allocated for the Integration environment, set the needed value in the .magento.app. yaml configuration file. Follow these steps:

1. On your local development environment, locate the .magento.app.yaml configuration file.
2. Open the file for editing using your plain text editor or IDE.
3. Set the new value for the disk key (in MB), for example:
   

   disk: 5120

4. Save changes in the file.
5. Git push the edited file to your Integration environment.

The changes come into effect after you Git push the updated YAML file to the environment.

Add services and allocate disk space for them

To add services for your Magento Cloud application, include the services, their versions, and the allocated disk space in the .magento/service.yaml configuration file. Follow these steps:

1. On your local development environment, locate the .magento/service.yaml configuration file.
2. Open the file for editing using your plain text editor or IDE.
3. Add a service, its version, and the required disk space (in MB) using this pattern:
   

   <service_name>:
           type: <service_name>:<service_version>
           disk: <disk_space_in_megabytes>
   

   For example, for the Redis service:

   redis:
           type: redis:3.0
           disk: 2048
   

4. Save changes in the file.
5. Git push the edited file to your Integration environment.