From 86c2917396e958fcd6efe2b44539629074a5ddcf Mon Sep 17 00:00:00 2001
From: mirdono <alexander.van.den.berghe@redpencil.io>
Date: Tue, 26 Nov 2024 17:19:13 +0100
Subject: [PATCH] chore: move db-cleanup configuration

Moved the `db-cleanup` configuration up so the two migration services are right
after each other again.
---
 docker-compose.yml | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/docker-compose.yml b/docker-compose.yml
index 3c3cd89..28a1da8 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -51,6 +51,15 @@ services:
       - "logging=true"
     restart: always
     logging: *default-logging
+  db-cleanup:
+    image: lblod/db-cleanup-service:0.5.1
+    environment:
+      MU_SPARQL_ENDPOINT: "http://db:8890/sparql"
+      CRON_PATTERN: "23 */6 * * *"
+    labels:
+      - "logging=true"
+    restart: always
+    logging: *default-logging
   migrations:
     image: semtech/mu-migrations-service:0.7.0
     links:
@@ -61,15 +70,6 @@ services:
       - "logging=true"
     restart: always
     logging: *default-logging
-  db-cleanup:
-    image: lblod/db-cleanup-service:0.5.1
-    environment:
-      MU_SPARQL_ENDPOINT: "http://db:8890/sparql"
-      CRON_PATTERN: "23 */6 * * *"
-    labels:
-      - "logging=true"
-    restart: always
-    logging: *default-logging
   migrations-triggering-indexing:
     image: semtech/mu-migrations-service:0.8.0
     links: