From 7ba7b6efda1ed86f92214a434cf1b25e1d4f6fc3 Mon Sep 17 00:00:00 2001 From: Jason Kulatunga Date: Thu, 9 Jun 2022 07:35:07 -0700 Subject: [PATCH] Update TROUBLESHOOTING_DOCKER.md --- docs/TROUBLESHOOTING_DOCKER.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/TROUBLESHOOTING_DOCKER.md b/docs/TROUBLESHOOTING_DOCKER.md index 75abb14..3fe620b 100644 --- a/docs/TROUBLESHOOTING_DOCKER.md +++ b/docs/TROUBLESHOOTING_DOCKER.md @@ -1,5 +1,8 @@ # Docker Images `master-omnibus` vs `latest` +> TL;DR; The `master-omnibus` and `latest` tags are almost semantically identical, as I follow a `golden master` +development process. However if you want to ensure you're only using the latest release, you can change to `latest` + The CI script used to orchestrate the docker image builds can be found here: https://github.com/AnalogJ/scrutiny/blob/master/.github/workflows/docker-build.yaml#L166-L184 In general Scrutiny follows a `golden master` development process, which means that the `master` branch is not directly updated (unless its for documentation changes), @@ -20,6 +23,3 @@ ignored -- https://github.com/AnalogJ/scrutiny/issues/287. That has since been f Hope that gives you an understanding for how everything is wired up. -TL;DR; The `master-omnibus` and `latest` tags are almost semantically identical, as I follow a `golden master` -development process. However if you want to ensure you're only using the latest release, you can change to `latest` -