4d4330fb3f
* fix(docker): make wait-for-api.sh POSIX and enforce LF line endings (#586) * fix: restore inline comment on final exit 0 Addresses review feedback: the comment on the final `exit 0` explains a non-obvious design decision (frontend still starts when the API never became ready, so users get a usable UI with connection errors rather than a dead container). --------- Co-authored-by: Luis Novo <lfnovo@gmail.com>
25 lines
891 B
Bash
Executable file
25 lines
891 B
Bash
Executable file
#!/bin/sh
|
|
# Wait for the API to be healthy before starting the frontend
|
|
# This prevents the "Unable to Connect to API Server" error during startup
|
|
# POSIX-compliant so it runs with /bin/sh (dash) in slim images
|
|
|
|
API_URL="${INTERNAL_API_URL:-http://localhost:5055}"
|
|
MAX_RETRIES=60
|
|
RETRY_INTERVAL=5
|
|
i=0
|
|
|
|
echo "Waiting for API to be ready at ${API_URL}/health..."
|
|
|
|
while [ $i -lt $MAX_RETRIES ]; do
|
|
if curl -s -f "${API_URL}/health" > /dev/null 2>&1; then
|
|
echo "API is ready! Starting frontend..."
|
|
exit 0
|
|
fi
|
|
i=$((i + 1))
|
|
echo "Attempt $i/$MAX_RETRIES: API not ready yet, waiting ${RETRY_INTERVAL}s..."
|
|
sleep $RETRY_INTERVAL
|
|
done
|
|
|
|
echo "ERROR: API did not become ready within $((MAX_RETRIES * RETRY_INTERVAL)) seconds"
|
|
echo "Starting frontend anyway - users may see connection errors initially"
|
|
exit 0 # Exit 0 so frontend still starts (better than nothing)
|