Make sure the bot auto restarts #171
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Whenever you flush or change your firewall, it drops iptables for docker annoyingly, or if you are using a service that affect the iptables in general can make docker unusable. When you restart docker, the restart command i added will make sure to restart the bot aswell. Without it, the bot will have to be manually started with docker-compose up -d
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Whenever you flush or change your firewall, it drops iptables for docker annoyingly, or if you are using a service that affect the iptables in general can make docker unusable.
When you restart docker, the restart command i added will make sure to restart the bot aswell. Without it, the bot will have to be manually started with
docker-compose up -d