You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 19, 2024. It is now read-only.
* Correct Manage disk space section (#7171)
moving to another branch for continued edits
* Update manage-disk-space.md
* Update manage-disk-space.md
Co-authored-by: Suman <[email protected]>
Copy file name to clipboardExpand all lines: src/cloud/project/manage-disk-space.md
+69-33Lines changed: 69 additions & 33 deletions
Original file line number
Diff line number
Diff line change
@@ -7,72 +7,104 @@ functional_areas:
7
7
---
8
8
You can find the total storage capacity for your Cloud project in your {{site.data.var.ece}} contract and on your [Magento account page](https://accounts.magento.cloud/user). Each project card in your account shows the number of _environments_, the _storage_ capacity in GB, and the number of _users_.
9
9
10
-
You can check disk space usage in each environment using the _disk free_ command, which reports the amount of disk space used by the file system. You must use SSH to log in to a remote environment.
10
+
## Check Integration environment
11
+
12
+
You can check disk space usage for your Integration environment using the `magento-cloud` CLI.
13
+
14
+
**To check approximate disk space usage:**
11
15
12
16
```bash
13
-
df -h
17
+
magento-cloud db:size
14
18
```
15
19
16
-
The `-h` option displays the report using a human-readable format (KB, MB, or GB).
For the database, you can use the {{ site.data.var.ece }} CLI to check approximate disk space usage:
55
+
## Check dedicated clusters
56
+
57
+
For Pro Staging and Production environments, you can check disk space usage in each environment using the _disk free_ command, which reports the amount of disk space used by the file system. You must use SSH to log in to a remote environment.
49
58
50
59
```bash
51
-
magento-cloud db:size
60
+
df -h
52
61
```
53
62
54
-
Sample response:
63
+
The `-h` option displays the report using a human-readable format (KB, MB, or GB).
64
+
65
+
In the following sample response, the `/data/exports/` mount shows the disk space for media and `/data/mysql/` mount shows disk space for the database:
Two configuration files control the allocation of disk space in the Cloud environments: the `.magento.app.yaml` file and the `.magento/services.yaml` file. Each file contains the `disk` property, which defines the disk size value in MB for the respective configuration.
69
101
70
102
{:.bs-callout-info}
71
-
You can change disk space allocation on Pro Integration and Starter enviroments only. You must submit a Magento support ticket to change disk space allocation on Pro Production and Staging environments.
103
+
You can change disk space allocation on Pro Integration and Starter environments only. You must submit a Magento support ticket to change disk space allocation on Pro Production and Staging environments.
72
104
73
105
### Application disk space
74
106
75
-
The `.magento.app.yaml` file controls the [persistent disk space]({{ site.baseurl }}/cloud/project/project-conf-files_magento-app.html#disk) available to the Magento application.
107
+
The `.magento.app.yaml` file controls the [persistent disk space][disk-key] available to the Magento application.
76
108
77
109
{:.procedure}
78
110
To increase disk space for your application:
@@ -124,7 +156,7 @@ To increase disk space for a service:
124
156
125
157
The changes take effect after you push the updated YAML file to the remote environment.
126
158
127
-
## Monitoring disk space
159
+
## Monitor disk space
128
160
129
161
On Pro Production environments, you can monitor disk space and other performance indicators using Adobe-generated alert policies for New Relic. For details, see [New Relic]({{ site.baseurl }}/cloud/project/new-relic.html).
130
162
@@ -135,3 +167,7 @@ The build cache can grow over time. If you receive a warning that states `No spa
0 commit comments