Protei/PromucFlow_constructor
2
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

fix: Fix backend failing to start when running with a custom PORT (#27461)

Browse Source 
When running with a custom `PORT` env variable, NGINX server will be
listening on this port. In the backend's startup script, `run-java.sh`,
we're checking for RTS being up or not, at `localhost`. So when the port
is not 80, then this will never succeed, because it'll be looking for
NGINX at the wrong port.

Instead, the fix here will make the backend startup script hit RTS
_directly_ on RTS server's own port, instead of going via NGINX. This
means it's independent of both the `PORT` env variable and the NGINX
server, and only dependent on RTS being up, which is really what we want
here.
This commit is contained in:
Shrikant Sharat Kandula 2023-09-20 10:27:54 +05:30 committed by GitHub
parent c15cade5b3
commit 1774557714
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
deploy/docker/fs/opt/appsmith/run-java.sh
View File

@ -54,7 +54,7 @@ if [[ $proxy_configured == 1 ]]; then
fi fi
# Wait until RTS started and listens on port 8091 # Wait until RTS started and listens on port 8091
while ! curl --fail --silent localhost/rts-api/v1/health-check; do while ! curl --fail --silent localhost:"${APPSMITH_RTS_PORT:-8091}"/rts-api/v1/health-check; do
echo 'Waiting for RTS to start ...' echo 'Waiting for RTS to start ...'
sleep 1 sleep 1
done done