From efe474e0e291c1e98fd9710514b4fe4132d5bd0a Mon Sep 17 00:00:00 2001
From: peaklabs-dev <122374094+peaklabs-dev@users.noreply.github.com>
Date: Wed, 9 Sep 2026 00:14:56 +0200
Subject: [PATCH] fix(docker): enable consistent naming for legacy custom
 container names

---
 ...ntainer_name_with_custom_internal_name.php | 21 +++++++++++++++++++
 1 file changed, 21 insertions(+)
 create mode 100644 database/migrations/2026_09_08_214510_align_consistent_container_name_with_custom_internal_name.php

diff --git a/database/migrations/2026_09_08_214510_align_consistent_container_name_with_custom_internal_name.php b/database/migrations/2026_09_08_214510_align_consistent_container_name_with_custom_internal_name.php
new file mode 100644
index 0000000000..30acb09200
--- /dev/null
+++ b/database/migrations/2026_09_08_214510_align_consistent_container_name_with_custom_internal_name.php
@@ -0,0 +1,21 @@
+<?php
+
+use Illuminate\Database\Migrations\Migration;
+use Illuminate\Support\Facades\DB;
+
+return new class extends Migration
+{
+    /**
+     * A stored custom container name was always used when deploying, even with consistent naming off, while
+     * the UI only shows the name in consistent naming mode. This migration enables consistent naming for those rows
+     * so they keep deploying with their custom name once the flag becomes the only switch.
+     */
+    public function up(): void
+    {
+        DB::table('application_settings')
+            ->whereNotNull('custom_internal_name')
+            ->where('custom_internal_name', '!=', '')
+            ->where('is_consistent_container_name_enabled', false)
+            ->update(['is_consistent_container_name_enabled' => true]);
+    }
+};