binary_desu

If your mainboard suports it you can use RTC alarm. I use the "custom command before sleep" field to execute the following one liner: echo $([ $(date +%H) -lt 5 ] && date -d "04:45" +%s || date -d "tomorrow 04:45" +%s) > /sys/class/rtc/rtc0/wakealarm this will wake my NAS every day at 04:45 to do backups etc. Another topic: anyone noticing the network detecetion not working? I tried all the interfaces and diffrent thresholds, but in de debug log it won't detect or even write anything related to network traffic. apperently the delay is checked before the network activity, i didnt realize that. nvrm

Life happens, no problem You do this on a voluntary base so nothing to worry about. Thank you for your work! 😁

Hi Guys, fithwum was last online in Oktober 2024, so i am not sure if this image is still supported. I cloned his gitlab repository and was able to build the image locally on my tower and got FoundryVTT v13 running. Here is how you can do it. Be wary, this is probably not the best solution, its just how i got it working. Also please ensure you backup your data, just in case! First open the shell on your tower and create a file named "Dockerfile" with following content: FROM alpine:latest LABEL maintainer="You" ENV PUID=99 ENV GUID=100 ENV GAME_PORT=30000 RUN adduser -D -u 99 -G users -h /foundry -s /bin/bash foundry # Install dependencies and folder creation RUN apk update && apk add --no-cache ca-certificates libstdc++ su-exec bash-completion tar nodejs npm \ && mkdir -p /foundry /ftemp \ && chmod 777 -R /foundry \ && chown 99:100 -R /foundry # Create script RUN cat > /ftemp/install_script.sh <<EOF mkdir -p /foundry/fvtt /foundry/data chown 99:100 -R /foundry chmod 776 -R /foundry chmod +x /foundry/ echo "INFO ! Starting FoundryVTT Server" echo " " su foundry -c 'node /foundry/fvtt/resources/app/main.js --dataPath=/foundry/data --ignore-gpu-blacklist' exit EOF # Set permissions RUN chmod +x /ftemp/install_script.sh \ && chown 99:100 -R /ftemp/install_script.sh # directory where data is stored VOLUME /foundry # TCP Port EXPOSE ${GAME_PORT} # Run command CMD [ "/bin/sh", "/ftemp/install_script.sh" ] This is basically the Dockerfile and install_script.sh from fithwum. Save it and then execute: docker build -f Dockerfile . -t foundryvtt_local:latest This will build the image and store it in your local docker repository under foundryvtt_local with the "latest" tag. Then Edit the docker container from fithwum and replace his repository with "foundryvtt_local:latest" It took some time for the fist start, but i was able to migrate my worlds und update systems/modules. I hope this will help! cheers

Hi! Your image needs an NodeJS update because FoundryVTT Version 13 requires Nodejs v20

🤦‍♂️you are right, i was too focused on the ENV. I ended up mounting a version of the start.sh which will execute source ./opt/scripts/user-start.sh that worked in the end. I have change that, replacing the ${GAME_PARAMS} via sed. Thank you!

Thanks for pointing me in the right direction. I was able to execute a script which will randomize the map part of the GAME_PARAMS ENV by mounting it as /opt/scripts/start-user.sh. However from my understanding i can't set the GAME_PARAMS environment variable from there because the start.sh script won't run the start-user.sh as source. It seems like i need to modify your start.sh script or the Dockerfile for my idea to work, which i wanted to avoid. I be glad if someone has another idea, but i think i will call it quits after 5h

I have a MapCycle.txt with my desired maps. The "problem" i want to solve is, that the server will always start with the same map defined in the GAME_PARAMS. For example GAME_PARAMS: "Ministry?Scenario=Scenario_Ministry_Checkpoint_Security?MaxPlayers=10?Password=xxx -GameStatsToken=xxxxx -GSLTToken=xxxx -GameStats -Mods -mutators=Hardcore,SoldierOfFortune,FullyLoaded,AIModifier -NoEAC -MapCycle" would cause that the first map after a (re-)start will always be Ministry, until we finish the map or i trigger a round win via the admin panel. What i want is that the first Map after a docker restart is random.

Hi ich777! Thank you very much for the template. I am using the insurgency sandstorm template. I would like the server to start with a random map on startup. To do this i tried to start a script similar to this https://github.com/zDestinate/INS_Sandstorm/blob/master/start.sh (my version just echoes a random string from the available maps/scenarios) and insert the output to the GAME_PARAMS variable. I tried some stuff but couldn't make it work, do you have any idea how i could achieve this?