I'm pretty sure janraasch isn't real and they are just 3 racoons in a trench coat.

.gitea/workflows/release.yaml

@@ -133,6 +133,10 @@ jobs:
       - name: Rename ARM Artifact
         run: mv app/dist/wolServer app/dist/wolServer-arm
 
+      - name: Generate Tag Name
+        id: tag
+        run: echo "TAG=v$(date +'%Y%m%d%H%M%S')" >> $GITEA_ENV
+
       - name: Create Release
         env:
           GITEA_TOKEN: ${{ secrets.mytoken }}
@@ -141,10 +145,10 @@ jobs:
           -H "Authorization: token ${{ secrets.mytoken }}" \
           -H "Content-Type: application/json" \
           -d '{
-            "tag_name": "v1.0.0",
+            "tag_name": "'"${{ env.TAG }}"'",
             "target_commitish": "main",
-            "name": "v1.0.0",
-            "body": "Release description",
+            "name": "'"${{ env.TAG }}"'",
+            "body": "Automated push release",
             "draft": false,
             "prerelease": false
           }'
@@ -185,8 +189,8 @@ jobs:
           docker ps -aq --filter "name=buildx" | xargs -r docker rm
           docker images --filter "reference=moby/buildkit" -q | xargs -r docker rmi
           docker images --filter "reference=arm-builder" -q | xargs -r docker rmi
-          docker images --filter "reference=gitea/runner-images" -q | xargs -r docker rmi
           docker images --filter "reference=multiarch/qemu-user-static" -q | xargs -r docker rmi
           docker images --filter "reference=tonistiigi/binfmt" -q | xargs -r docker rmi
           docker volume ls --filter "name=buildx" -q | xargs -r docker volume rm
           docker volume ls --filter "name=act" -q | xargs -r docker volume rm
+          docker images --filter "reference=gitea/runner-images" -q | xargs -r docker rmi

README.md

@@ -41,7 +41,16 @@ chmod +x setup.sh
 sudo ./setup.sh
 ```
 
-If you just want to use it and don't care about the code or you don't want to download any python dependencies, you can just grab the binary from the releases page and run it. The only real dependencies are a running Redis server, a correct .env file and a certs folder one directory behind with the certs. You can use the openssl lines of the setup.sh to achive that.
+If you just want to use it and don't care about the code or you don't want to download any python dependencies, you can just grab the binary from the releases page and run it. The easiest way to do that is this.
+
+```sh
+wget https://git.konsthol.eu/konsthol/WOL-Ly/raw/branch/main/setupSingleBinary.sh
+sudo bash setupSingleBinary.sh
+```
+
+When you change the .env in the app folder you should run this
+
+`sudo systemctl restart wolServer`
 
 ## Usage 🖥️