feat: dockerfile and github actions push to ghcr #5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a Dockerfile to build a docker image. Also, it creates a Github Actions workflow to push to the Github Container Registry. All of that is free for Open Source repositories and no extra configuration is needed in the repo to make it work.
You can check https://github.com/chainnodesorg/brevis-avs for an example and especially the below:
Actions Workflow:
https://github.com/chainnodesorg/brevis-avs/actions/workflows/dockerimage.yml
Github Container Registry:
https://github.com/chainnodesorg/brevis-avs/pkgs/container/brevis-avs
The workflow was made in a way that all pushes are built and tagged by commit hash, pushes to
main
are tagged aslatest
additionally and tag releases are tagged as the tag name additionally.That way multiple workflows are supported. e.g. Our fork version currently hosts a tagged docker image:
docker pull ghcr.io/chainnodesorg/brevis-avs:0.1.0
If merged and a git tag is pushed, the README can be extended to mention that official images are on the following:
ghcr.io/brevis-network/brevis-avs:0.1.0
Or any other tag.