Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate image to ghcr #63

Open
busykoala opened this issue Nov 9, 2023 · 2 comments
Open

Migrate image to ghcr #63

busykoala opened this issue Nov 9, 2023 · 2 comments

Comments

@busykoala
Copy link
Member

Since the integration with dockerhub is not ideal anymore we should migrate to ghcr.
Building and pushing the page could be easily done in a workflow like this:

name: Create and publish a Docker image

on:
  push:
    branches: ['main']

env:
  REGISTRY: ghcr.io
  IMAGE_NAME: ${{ github.repository }}

jobs:
  build-and-push-image:
    runs-on: ubuntu-latest
    permissions:
      contents: read
      packages: write
    steps:
      - name: Checkout repository
        uses: actions/checkout@v4
      - name: Log in to the Container registry
        uses: docker/login-action@65b78e6e13532edd9afa3aa52ac7964289d1a9c1
        with:
          registry: ${{ env.REGISTRY }}
          username: ${{ github.actor }}
          password: ${{ secrets.GITHUB_TOKEN }}
      - name: Extract metadata (tags, labels) for Docker
        id: meta
        uses: docker/metadata-action@9ec57ed1fcdbf14dcef7dfbe97b2010124a938b7
        with:
          images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}
      - 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 }}

The image will then be published to: ghcr.io/bespinian/bespinian.io:main

@qasimwarraich
Copy link
Member

qasimwarraich commented Feb 5, 2024

I like the idea, pushing to ghcr via an action is pretty painless. We could do something like this.

@busykoala
Copy link
Member Author

I'd wait util we decided what the future of our website will be, before we invest too much time here. Let's quickly sync and see in which direction we should push here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants