Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add github actions for container build and push. #41

Merged
merged 1 commit into from
Feb 6, 2025

Conversation

pantierra
Copy link
Collaborator

For the Cloud Deployment (#33) it would be convenient to build the container here and publish it on the github container registry, so we can pick it up with helm and kubernetes.

@pantierra pantierra force-pushed the feature/container-build-push branch from ee29f5c to e8f7185 Compare February 4, 2025 16:42
@pantierra pantierra force-pushed the feature/container-build-push branch from e8f7185 to b75b565 Compare February 4, 2025 16:45
@vincentsarago vincentsarago requested a review from dthiex February 4, 2025 16:54
@vincentsarago
Copy link
Collaborator

@dthiex is it ok if we push docker image in sentinel-hub GitHub registry?

@dthiex
Copy link
Collaborator

dthiex commented Feb 5, 2025

@dthiex is it ok if we push docker image in sentinel-hub GitHub registry?

@vincentsarago It's okay but please make sure to publish them as public package to avoid potential costs in the future.

GitHub Packages usage is free for public packages.

https://docs.github.com/en/billing/managing-billing-for-your-products/managing-billing-for-github-packages/about-billing-for-github-packages#about-billing-for-github-packages

@pantierra
Copy link
Collaborator Author

Requesting change of visibility of the package here: #42

@pantierra pantierra merged commit b9fe812 into main Feb 6, 2025
4 checks passed
@pantierra pantierra deleted the feature/container-build-push branch February 6, 2025 12:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants