An open-source, self-hostable PaaS alternative to Vercel, Heroku & Netlify that lets you easily deploy static sites, databases, full-stack applications and 360+ one-click services on your own servers.
PHP coolifydatabasesdeploymentdockerdocker-composeinertiajslaravelmariadbmysqlnextjsnodejsphppostgresredisself-hostedself-hostingserverstatic-sitesveltesvelte5
fix(docker): enable consistent naming for legacy custom container names
peaklabs-devefe474e0e291
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.phpnew file mode 100644index 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]);+ }+};