feat: create Dockerfile #222
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@josegonzalez I used the PyPI package previously, but it would make CI/CD difficult. eg Docker build would have to run after PyPI release, and pre-release Docker images might not be possible without manually updating the Dockerfile. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The resulting image can be used like
docker run ghcr.io/pl4nty/github-backup pl4nty --token $TOKEN. With some docs and a first-party image via GitHub Actions, this could close #211.It might also be usable for local development, but I'm not sure of the difference between
requirements.txtandrelease-requirements.txt. I used the latter.Build results: https://github.com/pl4nty/containers/actions/runs/6675073097/job/18142653711