name: Website containerize

on:
  push:
    branches:
      - master
# copied everything below this line from https://docs.github.com/en/actions/publishing-packages/publishing-docker-images
env:
  REGISTRY: ghcr.io
  IMAGE_NAME: ${{ github.repository }}

# There is a single job in this workflow. It's configured to run on the latest available version of Ubuntu.
jobs:
  build-and-push-image:
    runs-on: ubuntu-latest
    # Sets the permissions granted to the `GITHUB_TOKEN` for the actions in this job.
    permissions:
      contents: read
      packages: write
      # 
    steps:
      - name: Checkout repository
        uses: actions/checkout@v3
        with:
          submodules: true
      # 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
          # https://github.com/docker/metadata-action#basic
          tags: user/website_frontend:latest , user/website_frontend:{{steps.meta.outputs.sha}}
          labels: ${{ steps.meta.outputs.labels }}
            #jobs:
            #  build:
            #    runs-on: ubuntu-latest
            #    steps:
      ## old steps when I was deploying straight to VPS
      #      - name: Code Checkout
      #        uses: actions/checkout@v2
      #        with:
      #          submodules: true
      #          fetch-depth: 0
      #      - name: Hugo Setup
      #        uses: peaceiris/actions-hugo@v2
      #        with:
      #          hugo-version: '0.91.2'
      #      - name: Build
      #        run: hugo --minify
      #      - name: Clean
      #        uses: appleboy/ssh-action@master
      #        with:
      #          host: pagwin.xyz
      #          username: website
      #          key: ${{secrets.SSH_KEY}}
      #          script: rm -rf /var/www/pagwin.xyz/*
      #      - name: Deploy
      #        uses: up9cloud/action-rsync@master
      #        env:
      #          HOST: pagwin.xyz
      #          USER: website
      #          KEY: ${{secrets.SSH_KEY}}
      #          SOURCE: ./public/*
      #          TARGET: /var/www/pagwin.xyz/
      #