remove arv/v7 from platform targets

Author: jaredcat

.github/workflows/publish.yml

@@ -1,9 +1,4 @@
-# GitHub recommends pinning actions to a commit SHA.
-# To get a newer version, you will need to update the SHA.
-# You can also reference a tag or branch, but the action may change without warning.
-
 name: Publish Docker image
-
 on:
   push:
     branches:
@@ -18,18 +13,20 @@ jobs:
     steps:
       - name: Get current date
         run: echo "curr_date=$(date --utc +%Y-%m-%dT%H:%M:%SZ)" >> $GITHUB_ENV
+
       - name: Set up QEMU
         uses: docker/setup-qemu-action@v3
+
       - name: Set up Docker Buildx
         uses: docker/setup-buildx-action@v3
+
       - name: Login to ghcr.io
         uses: docker/login-action@v3
         with:
           registry: ghcr.io
           username: ${{ github.repository_owner }}
           password: ${{ secrets.GITHUB_TOKEN }}
-      - name: Checkout
-        uses: actions/checkout@v4
+
       - name: Build and push ${{github.event.release.tag_name }}
         id: docker_build_release
         uses: docker/build-push-action@v5
@@ -39,7 +36,7 @@ jobs:
           pull: true
           push: true
           tags: ghcr.io/mangosango/clive:latest,ghcr.io/mangosango/clive:${{ github.event.release.tag_name }}
-          platforms: linux/amd64,linux/arm64,linux/arm/v7
+          platforms: linux/amd64,linux/arm64
           provenance: false
           build-args: |
             VERSION=${{ github.event.release.tag_name }}
@@ -58,7 +55,7 @@ jobs:
           pull: true
           push: true
           tags: ghcr.io/mangosango/clive:main
-          platforms: linux/amd64,linux/arm64,linux/arm/v7
+          platforms: linux/amd64,linux/arm64
           provenance: false
           build-args: |
             VERSION=main

compose.yaml

@@ -1,15 +1,6 @@
-# Comments are provided throughout this file to help you get started.
-# If you need more help, visit the Docker Compose reference guide at
-# https://docs.docker.com/go/compose-spec-reference/
-
-# Here the instructions define your application as a service called "server".
-# This service is built from the Dockerfile in the current directory.
-# You can add other services your application may depend on here, such as a
-# database or a cache. For examples, see the Awesome Compose repository:
-# https://github.com/docker/awesome-compose
 services:
   clive:
-    env_file: .env
+    image: ghcr.io/mangosango/clive:latest
     volumes:
       - /path/to/db_and_logs_folder:/config
     # environment:
@@ -26,36 +17,4 @@ services:
     #   RICH_EMBED: true
     #   URL_AVATAR: http://i.imgur.com/9s3TBNv.png
     #   BOT_USERNAME: "Clive"
-
-
-# The commented out section below is an example of how to define a PostgreSQL
-# database that your application can use. `depends_on` tells Docker Compose to
-# start the database before your application. The `db-data` volume persists the
-# database data between container restarts. The `db-password` secret is used
-# to set the database password. You must create `db/password.txt` and add
-# a password of your choosing to it before running `docker-compose up`.
-#     depends_on:
-#       db:
-#         condition: service_healthy
-#   db:
-#     image: postgres
-#     restart: always
-#     user: postgres
-#     secrets:
-#       - db-password
-#     volumes:
-#       - db-data:/var/lib/postgresql/data
-#     environment:
-#       - POSTGRES_DB=example
-#       - POSTGRES_PASSWORD_FILE=/run/secrets/db-password
-#     expose:
-#       - 5432
-#     healthcheck:
-#       test: [ "CMD", "pg_isready" ]
-#       interval: 10s
-#       timeout: 5s
-#       retries: 5
-# volumes:
-#   db-data:
-
-
+    # env_file: .env      # Alternatly use a .env file