From df48f1a9c1a8816aedd8ce886bc1a0cb0dc04c79 Mon Sep 17 00:00:00 2001 From: Joe Corall Date: Tue, 2 Jan 2024 12:29:57 -0500 Subject: [PATCH] Update README --- README.md | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index d3f83aa..1d69e7d 100644 --- a/README.md +++ b/README.md @@ -5,23 +5,22 @@ Various docker containers used within Lehigh Libraries infrastructure. ## Structure ``` -|-- ./.github/workflows/image1.yml -|-- ./.github/workflows/image2.yml -... -... -... -|-- ./.github/workflows/imageN.yml |-- ./image1 | `-- ./image1/Dockerfile +| `-- ./image1/.build-args/TAG1 +| `-- ./image1/.build-args/TAG2 |-- ./image2 | `-- ./image2/Dockerfile +| `-- ./image2/.build-args/TAG1 ... ... ... |-- ./imageN | `-- ./imageN/Dockerfile +| `-- ./imageN/.build-args/TAG1 + ``` Each docker image is defined within its own directory. -The image then has a GitHub action defined in [.github/workflows](./.github/workflows) that uses the base [build-push GitHub Action workflow](./.github/workflows/build-push.yml) to push images to Google Artifact Registry. +The image then has a `.build-args` directory. That directory contains a file that is represents a specific version for the tag. The file then contains any `build-args` that may be needed for the docker build.