chore: push to gh container registry

This approach essentially works the same as the one in the previous
commit, but allows more control over the name of the package as it
appears in the org packages tab and repo packages.

.github/workflows/deploy.yml

@@ -37,18 +37,14 @@ jobs:
       - name: Build theme
         run: npm run build:prod
 
-      - name: Set up Docker Buildx
-        uses: docker/setup-buildx-action@v3
-
-      - name: Build and export
-        uses: docker/build-push-action@v5
-        with:
-          context: .
-          tags: myimage:latest
-          outputs: type=docker, dest=/tmp/myimage.tar
-
-      - name: Upload artifact
-        uses: actions/upload-artifact@v3
+      - name: 'Login to GitHub Container Registry'
+        uses: docker/login-action@v1
         with:
-          name: myimage
-          path: /tmp/myimage.tar
+          registry: ghcr.io
+          username: ${{github.actor}}
+          password: ${{secrets.GH_TOKEN}}
+
+      - name: 'Build Inventory Image'
+        run: |
+          docker build . --tag ghcr.io/sparkbox/sparkpress:latest
+          docker push ghcr.io/sparkbox/sparkpress:latest

Dockerfile

@@ -1,5 +1,7 @@
 FROM php:8.1-apache-buster
 
+LABEL org.opencontainers.image.source=https://github.com/sparkbox/sparkpress-wordpress-starter
+
 # When changings, also change in .circleci/config.yml
 ENV WP_VERSION=6.3.1
 
@@ -34,4 +36,4 @@ RUN find /var/www/ -type f -exec chmod 644 {} \;
 
 # make the linters executable so we can run them from containers
 RUN chmod +x vendor/bin/phpcs
-RUN chmod +x vendor/bin/twigcs
+RUN chmod +x vendor/bin/twigcs