CI/gitiea ci compatibility (#1)
CI / Generate Certificates (push) Successful in 26s
CI / Frontend CI (push) Successful in 1m16s
CI / Backend CI (push) Successful in 1m9s
CI / E2E Tests (push) Has been skipped

Co-authored-by: me <ramvignesh-b@github.com>
Co-authored-by: ramvignesh-b <ramvignesh-b@github.com>
Reviewed-on: #1
This commit was merged in pull request #1.
This commit is contained in:
2026-05-05 14:46:00 +00:00
parent c7764952d8
commit 740753cb33
2 changed files with 50 additions and 23 deletions
+12
View File
@@ -55,6 +55,18 @@ until $CONTAINER_BIN exec "$DB_NAME" pg_isready -U "${DB_USER:-test}" >/dev/null
done
export PIKU_ENV_FILE="$ENV_FILE"
# NOTE: When running in Gitea Actions (within container), We must ponint DB and mail to the internal docker host instead.
if [ "$GITEA_ACTIONS" = "true" ]; then
sudo apt-get update && sudo apt-get install -y iproute2
# Sample: "default via <internal docker host IP> dev <network interface> proto dhcp src <IP> metric 100"
HOST_IP=$(ip route show default | awk '/default/ {print $3}')
echo "Running on Gitea. Internal Docker host... $HOST_IP"
export DB_HOST=$HOST_IP
export EMAIL_HOST=$HOST_IP
fi
echo "Starting Backend..."
mkdir -p ./tmp/logs
(