From 6b3719bf28a7e445029c07cf232de151867ec8db Mon Sep 17 00:00:00 2001
From: GuavaPopper <radityaindraputranto@gmail.com>
Date: Fri, 12 Jun 2026 14:53:23 +0700
Subject: [PATCH] fix: increase db healthcheck start_period to 360s for
 first-boot init

MySQL first-boot InnoDB init + schema.sql takes ~6 minutes.
Previous config only allowed 130s total (30s start_period + 20x5s),
causing container to be marked unhealthy before MySQL was ready.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---
 docker-compose.yaml | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docker-compose.yaml b/docker-compose.yaml
index d3634fc..b2f0356 100644
--- a/docker-compose.yaml
+++ b/docker-compose.yaml
@@ -37,10 +37,10 @@ services:
       - mysql-data:/var/lib/mysql
     healthcheck:
       test: ["CMD-SHELL", "mysqladmin ping -h localhost -uroot -p\"$${MYSQL_ROOT_PASSWORD}\" --silent"]
-      interval: 5s
+      interval: 10s
       timeout: 5s
-      retries: 20
-      start_period: 30s
+      retries: 30
+      start_period: 360s
 
 volumes:
   mysql-data: