From 80d432171d8593529654bb5ebb5bc31708392085 Mon Sep 17 00:00:00 2001
From: OZCAP <48883102+OZCAP@users.noreply.github.com>
Date: Sat, 13 Dec 2025 10:43:35 +0400
Subject: [PATCH] fix: use original_server for log drain config in
 generate_compose_file

When build server is enabled, $this->server points to the build server.
The log drain configuration check was using $this->server which would
incorrectly check the build server's settings instead of the deployment
server where the container actually runs.

This fix ensures log drain configuration is correctly applied based on
the deployment server's settings by using $this->original_server.
---
 app/Jobs/ApplicationDeploymentJob.php | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/app/Jobs/ApplicationDeploymentJob.php b/app/Jobs/ApplicationDeploymentJob.php
index cc1a44f9a..7e2cb8e9c 100644
--- a/app/Jobs/ApplicationDeploymentJob.php
+++ b/app/Jobs/ApplicationDeploymentJob.php
@@ -2613,7 +2613,7 @@ private function generate_compose_file()
         } else {
             $docker_compose['services'][$this->container_name]['labels'] = $labels;
         }
-        if ($this->server->isLogDrainEnabled() && $this->application->isLogDrainEnabled()) {
+        if ($this->original_server->isLogDrainEnabled() && $this->application->isLogDrainEnabled()) {
             $docker_compose['services'][$this->container_name]['logging'] = generate_fluentd_configuration();
         }
         if ($this->application->settings->is_gpu_enabled) {