This PR automates the release process. Now, when a GitHub release is published a GitHub Actions workflow will build the Docker image for this new version and publish it (docker push) in DockerHub.
In order to do this we need to add 3 secrets to this repository:
Every image will be tagged with: latest, git-tag and commit-short-sha. Now the image version will be handled with tags instead of the image name (because this is a bad practice). Below some examples:
cabolabs/ehrserver or cabolabs/ehrserver:latest (always point to the latest version)
cabolabs/ehrserver:v2.3 (image tag equals to github tag)
cabolabs/ehrserver:835cef5 (image tag is the github commit sha, in short format)
This PR automates the release process. Now, when a GitHub release is published a GitHub Actions workflow will build the Docker image for this new version and publish it (
docker push) in DockerHub.In order to do this we need to add 3 secrets to this repository:
DOCKER_USERNAME: DockerHub account usernameDOCKER_PASSWORD: DockerHub passwordDOCKER_REPO: Target repository (i.e.cabolabs/ehrserver)Every image will be tagged with:
latest,git-tagandcommit-short-sha. Now the image version will be handled with tags instead of the image name (because this is a bad practice). Below some examples: