V13 main.js path compatibility + docker image enhancements.

Preparing environment for building different Foundry dockers using a build argument to choose which node base image is being applied. Not strictly required right now, but might be useful in the future.

.gitea/workflows/build-docker-image-and-push.yaml

@@ -26,9 +26,18 @@ jobs:
           username: ${{ secrets.REGISTRY_USERNAME }}
           password: ${{ secrets.REGISTRY_PASS }}
       -
-        name: Build and push
+        name: Build and push v12 compatible build
         uses: docker/build-push-action@v5
         with:
           context: .
           push: true
-          tags: gitea.crovaxon.de/crovaxon/foundryvtt-docker
+          tags: gitea.crovaxon.de/crovaxon/foundryvtt-docker:v12
+          build-args: NODE_IMAGE_VERSION=20-alpine
+      -
+        name: Build and push v12 compatible build
+        uses: docker/build-push-action@v5
+        with:
+          context: .
+          push: true
+          tags: gitea.crovaxon.de/crovaxon/foundryvtt-docker:v13,gitea.crovaxon.de/crovaxon/foundryvtt-docker:latest
+          build-args: NODE_IMAGE_VERSION=22-alpine

Dockerfile

@@ -1,4 +1,5 @@
-FROM node:20-alpine
+ARG NODE_IMAGE_VERSION=20-alpine
+FROM node:${NODE_IMAGE_VERSION}
 LABEL maintainer="crovaxon"
 
 WORKDIR /app

entrypoint.sh

@@ -6,5 +6,13 @@ umask ${UMASK}
 # set permissions on application folder 
 chown -R ${PUID}:${PGID} /foundry
 
+# set default main.js path as used in v12 and earlier
+FOUNDRY_MAIN_PATH=/foundry/resources/app/main.js
+
+# check for newer path used in v13 and newer
+if [ ! -f /foundry/main.js ]; then
+    FOUNDRY_MAIN_PATH=/foundry/main.js
+fi
+
 # run Foundry with the environmentally set user and group id
-exec su-exec ${PUID}:${PGID} node /foundry/resources/app/main.js --dataPath=/foundrydata
+exec su-exec ${PUID}:${PGID} node $FOUNDRY_MAIN_PATH --dataPath=/foundrydata