me/pi-ku
1
0
Fork 0
mirror of https://github.com/ramvignesh-b/pi-ku.git synced 2026-05-04 20:43:48 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

chore: configure Gitea Actions network routing in e2e

Browse Source
This commit is contained in:
ramvignesh-b
2026-05-05 00:02:56 +05:30
parent f0d9793fc3
commit 0681a785a5
1 changed files with 12 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
scripts/run-e2e.sh
+12
View File
@@ -55,6 +55,18 @@ until $CONTAINER_BIN exec "$DB_NAME" pg_isready -U "${DB_USER:-test}" >/dev/null
done done
export PIKU_ENV_FILE="$ENV_FILE" export PIKU_ENV_FILE="$ENV_FILE"
# NOTE: When running in Gitea Actions (within container), 127.0.0.1 is the actions instance.
# We must route DB and mail traffic to the docker hostinstead.
if [ "$GITEA_ACTIONS" = "true" ]; then
# Sample: "default via <internal docker host IP> dev <network interface> proto dhcp src <internal docker host 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..." echo "Starting Backend..."
mkdir -p ./tmp/logs mkdir -p ./tmp/logs
( (