SquadJSDocker/scripts/entry.sh

#!/bin/sh

printf "Starting SquadJS...\n"
sleep 10
/usr/bin/node --unhandled-rejections=strict ./index.js
fix: delay squadjs startup by 10 seconds We have to wait until the Squad server is initialized and has a full RCON connection up. This allows SquadJS to be started in tandem with a Squad docker image in docker compose without conflict. This is a bit hacky and a healthcheck would be superior, but there's a lot of instances to check in the Squad log to even verify if the RCON connection is good to go. Another potential way of doing this health check is to attempt to login into the rcon connection ourselves in a loop and then start SquadJS once that rcon connection succeeds (after closing the RCON connection we made). 2023-02-03 16:42:24 -06:00			`#!/bin/sh`

			`printf "Starting SquadJS...\n"`
Update entry.sh 2024-02-06 16:07:45 -06:00			`sleep 10`
update node.js launch options should help with squadjs getting an error on the RCON connection. option will exit the entire process upon an unhandled promise rejection. this will allow a restart with docker. 2023-02-10 09:15:46 -06:00			`/usr/bin/node --unhandled-rejections=strict ./index.js`
fix: delay squadjs startup by 10 seconds We have to wait until the Squad server is initialized and has a full RCON connection up. This allows SquadJS to be started in tandem with a Squad docker image in docker compose without conflict. This is a bit hacky and a healthcheck would be superior, but there's a lot of instances to check in the Squad log to even verify if the RCON connection is good to go. Another potential way of doing this health check is to attempt to login into the rcon connection ourselves in a loop and then start SquadJS once that rcon connection succeeds (after closing the RCON connection we made). 2023-02-03 16:42:24 -06:00