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
Copy file name to clipboardExpand all lines: docs/REQUIREMENTS.md
+27Lines changed: 27 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -120,6 +120,27 @@ Checks installed PHP and database (MariaDB/MySQL) versions against the [endoflif
120
120
121
121
The warning threshold is configurable (default: 6 months before EOL).
122
122
123
+
### Disk space
124
+
125
+
Checks free disk space (via `df`) against two used-space thresholds:
126
+
127
+
| Condition | Status |
128
+
|-----------|--------|
129
+
| Used space >= fail threshold (default: 95%) | FAIL |
130
+
| Used space >= warn threshold (default: 80%) | WARN |
131
+
| Otherwise | OK |
132
+
133
+
Two locations are checked:
134
+
135
+
-**Webspace**: the configured `requirements_disk_space_webspace_path` (defaults to `deploy_path`).
136
+
-**Database**: only when the resolved database host (see "Database grants" credential resolution above) is `127.0.0.1`/`localhost`, i.e. reachable from the deploy target. The data directory is read via `SHOW VARIABLES LIKE 'datadir'`. If the database lives on a separate host, this check is skipped, since disk usage on an arbitrary remote host cannot be read via SSH from the deploy target.
137
+
138
+
Like every other check in this recipe, FAIL/WARN are reported in the summary table only — they do not stop the `requirements:check` command itself. To block a deployment on disk space, wire the check into the deploy pipeline in the consuming project, e.g.:
0 commit comments