personal-website/.gitea/workflows/build.yaml

72 lines
3.4 KiB
YAML
Raw Normal View History

2024-07-07 21:46:02 +02:00
#
name: Build Docker Image and Deploy
# Configures this workflow to run every time a change is pushed to main.
on:
push:
branches: ["main"]
# Defines two custom environment variables for the workflow. These are used for the Container registry domain, and a name for the Docker image that this workflow builds.
env:
IMAGE_NAME: ${{ github.repository }}
jobs:
build-and-push-image:
2024-07-07 21:11:32 +02:00
name: Build Image and push to Registry
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@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@v3
with:
2024-07-07 21:14:28 +02:00
registry: ${{ vars.REGISTRY }}
username: ${{ secrets.DOCKER_USERNAME }}
password: ${{ secrets.DOCKER_PASSWORD }}
# 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@v5
with:
2024-07-07 21:14:28 +02:00
images: ${{ vars.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@v5
with:
context: .
push: true
tags: ${{ steps.meta.outputs.tags }}
2024-07-07 21:11:32 +02:00
labels: ${{ steps.meta.outputs.labels }}
deploy:
name: Deploy on webserver
runs-on: ubuntu-latest
needs: build-and-push-image
steps:
- name: Install SSH key for target server
uses: webfactory/ssh-agent@v0.9.0
with:
ssh-private-key: ${{ secrets.SSH_PRIV_KEY }}
- name: Login to registry
2024-07-07 22:19:09 +02:00
run: ssh ${{ vars.TARGET_USER }}@${{ vars.TARGET }} -o StrictHostKeyChecking=no "docker login -u ${{ secrets.DOCKER_USERNAME }} -p ${{ secrets.DOCKER_PASSWORD }} ${{ vars.REGISTRY }}"
2024-07-07 22:49:39 +02:00
- name: Docker Compose the image
run: ssh ${{ vars.TARGET_USER }}@${{ vars.TARGET }} -o StrictHostKeyChecking=no "docker compose up -d"
2024-07-07 21:11:32 +02:00
- name: Logout from registry
2024-07-07 22:19:09 +02:00
run: ssh ${{ vars.TARGET_USER }}@${{ vars.TARGET }} -o StrictHostKeyChecking=no "docker logout ${{ vars.REGISTRY }}"
2024-07-07 21:11:32 +02:00
- name: Clean old images
2024-07-07 22:19:09 +02:00
run: ssh ${{ vars.TARGET_USER }}@${{ vars.TARGET }} -o StrictHostKeyChecking=no "docker image prune -a"