Image Build auf gchr.io

Umstellung Build repo

.github/workflows/publish-barshare-gbfs.yml

@@ -1,53 +1,72 @@
-name: build & deploy publish-barshare-gbfs Docker image
+name: Docker Image CI
 
 on:
   push:
-    branches:
-      - main
+    branches: [ main ]
+  pull_request:
+    branches: [ main ]
+
+env:
+  REGISTRY: ghcr.io
+  IMAGE_NAME: ${{ github.repository }}
+
 
 jobs:
-  build:
-    runs-on: ubuntu-latest
-    steps:
-    - uses: actions/checkout@v2
-    - uses: docker/login-action@v1
-      with:
-        registry: registry.gitlab.tpwd.de
-        username: ${{ secrets.GITLAB_USERNAME }}
-        password: ${{ secrets.GITLAB_PASSWORD }}
-    - name: build moqo2gbfs Docker image
-      uses: docker/build-push-action@v2
-      with:
-        context: .
-        tags: moqo2gbfs
-    - name: build & publish publish-barshare-gbfs Docker image
-      uses: docker/build-push-action@v2
-      with:
-        context: publish-barshare-gbfs
-        push: true
-        tags: registry.gitlab.tpwd.de/tpwd/bb-navi/publish-barshare-gbfs
-  deploy:
+  build-and-push-image:
     runs-on: ubuntu-latest
-    needs:
-      - build
-    container: r.planetary-quantum.com/quantum-public/cli:2
-    env:
-      QUANTUM_USER: "${{ secrets.QUANTUM_USER }}"
-      QUANTUM_PASSWORD: "${{ secrets.QUANTUM_PASSWORD }}"
-      QUANTUM_ENDPOINT: "tpwd-bb-navi"
-      QUANTUM_STACK: "publish-barshare-gbfs-tpwd-bb-navi"
-      MOQO_ACCESS_TOKEN: "${{ secrets.MOQO_ACCESS_TOKEN }}"
-      MINIO_ACCESS_KEY: "${{ secrets.MINIO_ACCESS_KEY }}"
-      MINIO_SECRET_KEY: "${{ secrets.MINIO_SECRET_KEY }}"
+    # Sets the permissions granted to the `GITHUB_TOKEN` for the actions in this job.
+    permissions:
+      contents: read
+      packages: write
+      # 
     steps:
-      - uses: actions/checkout@v2
-      # https://twitter.com/derhuerst/status/1511660213111336961
-      - name: inline env vars to work around quantum-cli support
-        run: |
-          cd publish-barshare-gbfs
-          apk add --no-cache --upgrade docker-compose moreutils
-          docker-compose -f quantum-stack.yml config | sponge quantum-stack.yml
-      - name: deploy to bbnavi infrastructure
-        run: |
-          cd publish-barshare-gbfs
-          quantum-cli stacks update --create --wait
+      - name: Checkout repository
+        uses: actions/checkout@v4
+      # Uses the `docker/login-action` action to log in to the Container registry registry using the account and password that will publish the packages. Once published, the packages are scoped to the account defined here.
+      - name: Log in to the Container registry
+        uses: docker/login-action@65b78e6e13532edd9afa3aa52ac7964289d1a9c1
+        with:
+          registry: ${{ env.REGISTRY }}
+          username: ${{ github.actor }}
+          password: ${{ secrets.GITHUB_TOKEN }}
+      # This step uses [docker/metadata-action](https://github.com/docker/metadata-action#about) to extract tags and labels that will be applied to the specified image. The `id` "meta" allows the output of this step to be referenced in a subsequent step. The `images` value provides the base name for the tags and labels.
+      - name: Extract metadata (tags, labels) for Docker
+        id: meta
+        uses: docker/metadata-action@9ec57ed1fcdbf14dcef7dfbe97b2010124a938b7
+        with:
+          images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}
+      # This step uses the `docker/build-push-action` action to build the image, based on your repository's `Dockerfile`. If the build succeeds, it pushes the image to GitHub Packages.
+      # It uses the `context` parameter to define the build's context as the set of files located in the specified path. For more information, see "[Usage](https://github.com/docker/build-push-action#usage)" in the README of the `docker/build-push-action` repository.
+      # It uses the `tags` and `labels` parameters to tag and label the image with the output from the "meta" step.
+      - name: Build and push Docker image
+        uses: docker/build-push-action@f2a1d5e99d037542a71f64918e516c093c6f3fc4
+        with:
+          context: .
+          push: true
+          tags: ${{ steps.meta.outputs.tags }}
+          labels: ${{ steps.meta.outputs.labels }}
+  # deploy:
+  #   runs-on: ubuntu-latest
+  #   needs:
+  #     - build
+  #   container: r.planetary-quantum.com/quantum-public/cli:2
+  #   env:
+  #     QUANTUM_USER: "${{ secrets.QUANTUM_USER }}"
+  #     QUANTUM_PASSWORD: "${{ secrets.QUANTUM_PASSWORD }}"
+  #     QUANTUM_ENDPOINT: "tpwd-bb-navi"
+  #     QUANTUM_STACK: "publish-barshare-gbfs-tpwd-bb-navi"
+  #     MOQO_ACCESS_TOKEN: "${{ secrets.MOQO_ACCESS_TOKEN }}"
+  #     MINIO_ACCESS_KEY: "${{ secrets.MINIO_ACCESS_KEY }}"
+  #     MINIO_SECRET_KEY: "${{ secrets.MINIO_SECRET_KEY }}"
+  #   steps:
+  #     - uses: actions/checkout@v2
+  #     # https://twitter.com/derhuerst/status/1511660213111336961
+  #     - name: inline env vars to work around quantum-cli support
+  #       run: |
+  #         cd publish-barshare-gbfs
+  #         apk add --no-cache --upgrade docker-compose moreutils
+  #         docker-compose -f quantum-stack.yml config | sponge quantum-stack.yml
+  #     - name: deploy to bbnavi infrastructure
+  #       run: |
+  #         cd publish-barshare-gbfs
+  #         quantum-cli stacks update --create --wait