Build & publish docker images

Output of rest-server --version : master

What should rest-server do differently?

It would be great if there were up-to-date published docker images of the rest-server available for both amd64 and arm64 architectures.

What are you trying to do? What is your use case?

I'm using a docker image as the backend and I want it to be confident it's regularly kept up to date.

Did rest-server help you today? Did it make you happy in any way?

I have put together a Github actions workflow in my fork to automatically build and publish the rest-server to the ghcr.io registry.

This will automatically publish to your own ghcr.io registry without having to configure any credentials as it will use the Github Actions GITHUB_TOKEN.

The produced images will have standardized tags and labels as produced by the official docker/metadata-action

Here's a couple of build examples to see what this is doing:

Pushes to master:

• https://github.com/jinnko/rest-server/actions/runs/6580532884/job/17878709059
• https://github.com/jinnko/rest-server/actions/runs/6580704450/job/17879251349

When a release is published:

• https://github.com/jinnko/rest-server/actions/runs/6580795590/job/17879516649

And there's a schedule-based trigger to ensure a weekly image is created from the master branch to capture any OS or env level security patches that may be needed.

If you're happy with all this I will raise the changes in a PR.

Review the proposed .github/workflows/docker.yml in the linked fork and compare its triggers, metadata, and registry publishing setup with this repository. Verify that the workflow builds and publishes up-to-date images for amd64 and arm64, including release and scheduled builds, with standardized tags and labels.