diff options
| author | m-chandler <mchandler89@gmail.com> | 2019-11-09 08:57:56 +1000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-11-09 08:57:56 +1000 |
| commit | 7b64f2e79842e0b7bc1eb80ccc9c2f51c9226c5b (patch) | |
| tree | 261ea116413d84e70eff926be3bf22c638253fca | |
| parent | 088d0197265a59cee69d2b1293540786ecee6f04 (diff) | |
Update readme.md
| -rw-r--r-- | readme.md | 13 |
1 files changed, 12 insertions, 1 deletions
@@ -129,13 +129,24 @@ In the below example (Paris), `m5.large` looks like a good option. Try to create 
+### Restarting the Container
+
+Visit the ECS dashboard in the AWS Console.
+1. Clusters
+2. Click on the factorio Cluster
+3. Tick the factorio Service, click Update
+4. Tick the "Force new deployment" option
+5. Click Next step (three times)
+7. Click Update Service
+
### Basic Docker Debugging
If you SSH onto the server, you can run the following commands for debugging purposes:
-* `sudo docker restart $(docker ps -q --filter ancestor=factoriotools/factorio)` - Restart server.
* `sudo docker logs $(docker ps -q --filter ancestor=factoriotools/factorio)` - Check Factorio container logs.
+DO NOT restart the Factorio docker container via SSH method. This will cause ECS to restart the container *again*. Refer to restarting to container above.
+
## Thanks
Thanks goes out to [FactorioTools](https://github.com/factoriotools) ([and contributors](https://github.com/factoriotools/factorio-docker/graphs/contributors)) for maintaining the Factorio Docker images.
|