changing reference for the cache to organization

.github/workflows/docker-publish.yml

@@ -37,7 +37,7 @@ jobs:
           sudo rm -rf /opt/ghc
           sudo rm -rf "/usr/local/share/boost"
 
-        ##DOCKER_TAG secret is also latest, change if you need for example a test version. 
+        ##DOCKER_TAG secret is latest, change if you need for example a test version. 
         ##Remember to set back to latest after that. Preferably, avoid changing that,
         ##and instead push to your own account for testing         
       - name: Build and push Docker image
@@ -50,9 +50,9 @@ jobs:
             BASE_IMAGE=${{ env.BASE_IMAGE }}
             GITHUB_PAT=${{ secrets.PAT_GITHUB }}
             DOCKER_BUILDKIT=1
-          outputs: type=registry
           ##The registry cache backend is the inline cache++. This backend pushes cache artifacts as a separate image than the Docker image to a dedicated location in the registry.
           ##Contrary to the inline cache, the registry cache supports caching of intermediate layers in a multi-stage Docker build when configured with mode=max . This increases the chances of cache hits on subsequent builds.
           ##It also supports a host of options to control compression type, levels, and naming of the cache image etc. At the cost of some additional complexity to set up, this is the best-in-class caching solution for Docker builds.
-          cache-from: type=registry,ref=user/app:buildcache
-          cache-to: type=registry,ref=user/app:buildcache,mode=max
+          ##From https://www.blacksmith.sh/blog/cache-is-king-a-guide-for-docker-layer-caching-in-github-actions
+          cache-from: type=registry,ref=hdssandbox/app:buildcache
+          cache-to: type=registry,ref=hdssandbox/app:buildcache,mode=max