Alexander G.
Alexander G.
I get it now. 😁 Restarting the container should do the job?
That's completely normal to treat it like a crash. Closing the bot is signaling with SIGTERM or SIGINT to the process and kills it after a brief period of time...
Using `--restart=always` would restart the container in case it's crashing. [Docs here](https://docs.docker.com/config/containers/start-containers-automatically/#use-a-restart-policy)
@Haarolean @idinium96 Hello. I have issued a PR for this thing that can be tested on. I have explained in the PR what the caveats are. 
@Haarolean The dev branch received an update regarding this. If you still use Docker for this, please check if this works with the `tf2autobot/tf2autobot:ba85ccf97ff2947e6646f8b81575098fb8a8fdfd-16.13.0-alpine` tag as it's the head of...
I have forked your repo on my profile a while ago. I can take time to work with it.
I agree, there should be some reference list for all the configurable variables. For your use case, it's simply `PORT` and you should change the `-p` Docker argument.
> The crucial change is using ' around the brackets for the ADMINS variable. I think the issue was with how bash was interpreting the space after [{steam:. Passing the...
I've had an `envFrom` idea before, but got over it as it was easily to be set using macros like `$container->setEnvFrom([['secretRef' => ...]])`. If anyone got a PR, I'll happily...
@Sammyjo20 Yeah, I actually reconsidered it since I've recently came back to become more involved into the project, so first steps are to have a proper cleanup of the issues...