fix: update references to docker-compose file and remove unused compose files

.env.coolify.example

@@ -2,7 +2,7 @@
 # Coolify Environment Variables — ClinicPro (Docker Compose)
 # ------------------------------------------------------------
 # Copy these into the Coolify resource's "Environment Variables" tab.
-# Only the variables referenced as ${...} in docker-compose.coolify.yaml
+# Only the variables referenced as ${...} in docker-compose.yml
 # need to be set here. DATABASE_URL / MESSENGER_TRANSPORT_DSN / REDIS_URL
 # are built INSIDE the compose file from the mariadb/redis service names.
 # ============================================================

compose.override.yaml

@@ -1,7 +0,0 @@
-
-services:
-###> doctrine/doctrine-bundle ###
-  database:
-    ports:
-      - "5432"
-###< doctrine/doctrine-bundle ###

compose.yaml

@@ -1,25 +0,0 @@
-
-services:
-###> doctrine/doctrine-bundle ###
-  database:
-    image: postgres:${POSTGRES_VERSION:-16}-alpine
-    environment:
-      POSTGRES_DB: ${POSTGRES_DB:-app}
-      # You should definitely change the password in production
-      POSTGRES_PASSWORD: ${POSTGRES_PASSWORD:-!ChangeMe!}
-      POSTGRES_USER: ${POSTGRES_USER:-app}
-    healthcheck:
-      test: ["CMD", "pg_isready", "-d", "${POSTGRES_DB:-app}", "-U", "${POSTGRES_USER:-app}"]
-      timeout: 5s
-      retries: 5
-      start_period: 60s
-    volumes:
-      - database_data:/var/lib/postgresql/data:rw
-      # You may use a bind-mounted host directory instead, so that it is harder to accidentally remove the volume and lose all your data!
-      # - ./docker/db/data:/var/lib/postgresql/data:rw
-###< doctrine/doctrine-bundle ###
-
-volumes:
-###> doctrine/doctrine-bundle ###
-  database_data:
-###< doctrine/doctrine-bundle ###

docker-compose.yml

@@ -1,5 +1,7 @@
 # Coolify deployment — Build Pack: Docker Compose
-# Select THIS file as the Compose file in the Coolify resource settings.
+# This is the production deploy stack (MariaDB + Redis). The ddev local env uses
+# its own compose.yaml; do not confuse the two.
+# Select this file (docker-compose.yml) as the Compose file in the Coolify resource.
 # Do NOT define custom `networks:` — Coolify manages the network; custom ones
 # break Traefik routing (per Coolify docs).
 

docs/deploy/coolify.md

@@ -2,14 +2,14 @@
 
 این راهنما نحوهٔ دیپلوی بک‌اند ClinicPro (Symfony 7.4 + پنل React) را روی **Coolify** با Build Pack از نوع **Docker Compose** توضیح می‌دهد.
 
-> همهٔ فایل‌های دیپلوی در ریشهٔ ریپو هستند: `Dockerfile`، `docker-compose.coolify.yaml`، پوشهٔ `docker/` و `.env.coolify.example`.
+> همهٔ فایل‌های دیپلوی در ریشهٔ ریپو هستند: `Dockerfile`، `docker-compose.yml`، پوشهٔ `docker/` و `.env.coolify.example`.
 > فایل‌های `compose.yaml`، `compose.override.yaml` و `.ddev/` مخصوص محیط لوکال (ddev) هستند و **در دیپلوی نقشی ندارند**.
 
 ---
 
 ## معماری دیپلوی
 
-`docker-compose.coolify.yaml` پنج سرویس بالا می‌آورد:
+`docker-compose.yml` پنج سرویس بالا می‌آورد:
 
 | سرویس | نقش | نکته |
 |-------|-----|------|
@@ -32,7 +32,7 @@
 3. در تنظیمات:
    - **Branch:** `main`
    - **Base Directory:** `/` (ریشهٔ ریپو)
-   - **Docker Compose File:** `docker-compose.coolify.yaml`
+   - **Docker Compose File:** `docker-compose.yml`
 
 ### ۲. اختصاص دامنه