Some OMO stuff and a release workflow
This commit is contained in:
@@ -0,0 +1,41 @@
|
||||
# Builds the image and pushes it. It does not deploy.
|
||||
#
|
||||
# What picks it up is a timer on the server (see `deploy/`), so nothing here
|
||||
# holds a credential for the machine it runs on and a bad build cannot take the
|
||||
# service down by itself. The trade is that a deploy happens a few minutes
|
||||
# after the push rather than at the moment of it.
|
||||
|
||||
name: Image
|
||||
|
||||
on:
|
||||
push:
|
||||
branches:
|
||||
- main
|
||||
|
||||
jobs:
|
||||
image:
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- uses: actions/checkout@v4
|
||||
|
||||
- uses: docker/setup-buildx-action@v3
|
||||
|
||||
- uses: docker/login-action@v3
|
||||
with:
|
||||
registry: ${{ vars.REGISTRY }}
|
||||
username: ${{ vars.USERNAME }}
|
||||
password: ${{ secrets.DOCKER_PASSWORD }}
|
||||
|
||||
# Tagged with the commit as well as `latest`, so that "what is actually
|
||||
# running" has an answer, and so a rollback is a tag rather than a revert
|
||||
# and a rebuild.
|
||||
- uses: docker/build-push-action@v5
|
||||
with:
|
||||
context: .
|
||||
file: ./Dockerfile
|
||||
push: true
|
||||
tags: |
|
||||
${{ vars.REGISTRY }}/connor/news:latest
|
||||
${{ vars.REGISTRY }}/connor/news:${{ github.sha }}
|
||||
cache-from: type=gha
|
||||
cache-to: type=gha,mode=max
|
||||
Reference in New Issue
Block a user