Made the restart policies of Docker containers more consistent #94
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.
Description
I tried using Anytype as my own self-hosted note app and encountered an issue. When I deployed Anytype following the instructions in the README.md, the cluster worked well initially. However, after rebooting the VM, I noticed that while some Docker containers automatically started, others did not (specifically, Mongo, Coordinator, and Tools). After a brief investigation, I realized that the 'restart' policies of the containers were inconsistent. I have prepared this PR to address and fix this inconsistency.
Impact analysis: Based on the README.md, this project is intended for development and launching small personal clusters. I believe my changes will not negatively impact any users.
What type of PR is this? (check all applicable)
Related Tickets & Documents
Mobile & Desktop Screenshots/Recordings
Added tests?
Added to documentation?
[optional] Are there any post-deployment tasks we need to perform?