From 9c4a9ea904110cc8758268acce9f571e5b50f0fe Mon Sep 17 00:00:00 2001
From: Fabian Arrotin <arrfab@centos.org>
Date: Nov 26 2024 09:01:19 +0000
Subject: Adding doc snippet about container.specs and how to ensure running good container


Signed-off-by: Fabian Arrotin <arrfab@centos.org>

---

diff --git a/README.md b/README.md
index 238fafb..188fd86 100644
--- a/README.md
+++ b/README.md
@@ -36,6 +36,9 @@ Let's first clone git repo and ensure that some files in container will be owned
 
 ## Running
 
+It's worth knowing that this git repository contains a `container.specs` that you should use (source it) to ensure you point to correct container path/tag (see below)
+Using that tag permits to also just test , based on branch, by updating that `container.specs` file, the container path but also version to use.
+
 ### Development
 
 The better way to work on local changes is to have jekyll to automatically
@@ -44,12 +47,14 @@ that files were added/modified. To do this, and then to be able to browse
 "live" on http://localhost:4000, launch Jekyll like this:
 
 ```
-install -d public
+cd ${git_directory}/centos.org
+source container.specs
+podman images --format "{{.Repository}}:{{.Tag}}"|grep -q ${container_path}:${container_tag} || podman pull ${container_path}:${container_tag}
 podman run --rm -d \
     --name jekyll-theme-centos-site-server \
     -v $PWD/:/site:z \
     -p 0.0.0.0:4000:4000 \
-    registry.gitlab.com/centos/artwork/centos-web/jekyll-theme-centos:latest \
+    ${container_path}:${container_tag} \
     bundle exec jekyll serve -H 0.0.0.0 -p 4000 --config /site/_config.yml -s /site -d /site/_site
 ```
 
@@ -64,7 +69,6 @@ expose the `${git_directory}/centos.org/_site/` directory as document root, the
 place where jekyll build command renders the final files.
 
 ```
-install -d public
 podman run --rm -d \
     --name jekyll-theme-centos-site \
     -v $PWD/:/site:z \