Validate Docker Compose configurations without starting containers

.github/workflows/validate-compose.yml

@@ -0,0 +1,30 @@
+name: Validate Docker Compose
+
+on:
+  push:
+    branches:
+      - main
+  pull_request:
+  workflow_dispatch:
+
+permissions:
+  contents: read
+
+jobs:
+  validate-compose:
+    runs-on: ubuntu-24.04
+    timeout-minutes: 5
+    steps:
+      - name: Check out repository
+        uses: actions/checkout@v7
+        with:
+          persist-credentials: false
+
+      - name: Validate Compose configurations
+        shell: bash
+        run: |
+          docker compose version
+          for config in testops*/docker-compose.yml; do
+            echo "Validating $config"
+            docker compose --env-file "${config%/*}/env-example" -f "$config" config --quiet
+          done

README.md

@@ -72,11 +72,21 @@ Use this configuration if you are going to manage end users and their authentica
 | Redis       | preferably standalone server |
 | S3 solution | standalone server            |
 
+## Configuration validation
+
+GitHub Actions validates all `testops*/docker-compose.yml` files on pushes to `main` and pull requests using `docker compose config --quiet` and each configuration's `env-example`. This checks YAML syntax and the Compose model without pulling images or starting containers.
+
+To validate a configuration locally, run from the repository root:
+
+```sh
+docker compose --env-file testops/env-example -f testops/docker-compose.yml config --quiet
+```
+
 ## Upgrade from version 4 to version 5
 
 The only available paths from to upgrade 4 to 5 are
 
 - 4.25.1 → 5.3.3, then to next available version
 - 4.26.1 → 5.3.3 then to next available version
 
-Upgrade process is thoroughly described in [TestOps documentation here.](https://docs.qameta.io/allure-testops/migrations/to-5/)
+Upgrade process is thoroughly described in [TestOps documentation here.](https://docs.qameta.io/allure-testops/migrations/to-5/)