From c37fdb9f1c86e3b94584c5ed17c945b44dd9b7f5 Mon Sep 17 00:00:00 2001
From: Trisha Anand <trisha@appsmith.com>
Date: Fri, 8 Apr 2022 18:48:23 +0530
Subject: [PATCH] fix: Only setting maximum heap size for heroku deployed
 instances (#12725)

Co-authored-by: Arpit Mohan <mohanarpit@users.noreply.github.com>
---
 deploy/docker/entrypoint.sh | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/deploy/docker/entrypoint.sh b/deploy/docker/entrypoint.sh
index f6014b86e8..b8a2b577e4 100755
--- a/deploy/docker/entrypoint.sh
+++ b/deploy/docker/entrypoint.sh
@@ -224,12 +224,13 @@ if [[ -z "${DYNO}" ]]; then
   # Don't run MongoDB if running in a Heroku dyno.
   init_mongodb
   init_replica_set
+else 
+  # These functions are used to limit heap size for Backend process when deployed on Heroku
+  get_maximum_heap
+  setup_backend_heap_arg
 fi
 mount_letsencrypt_directory
 check_redis_compatible_page_size
-# These functions are used to limit heap size for Backend process when deployed on Heroku
-get_maximum_heap
-setup_backend_heap_arg
 configure_supervisord
 
 CREDENTIAL_PATH="/etc/nginx/passwords"