-
Notifications
You must be signed in to change notification settings - Fork 95
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
GitHub Actions publish #58
Comments
This is a great idea but I'm not sure how it'd be helpful when you'll need access to the code. |
@rednafi Access to the code how? Could you elaborate? |
@ayr-ton This application is pretty basic at what it does. However, it's extensible. So, if I push this as a container, what purpose that'd serve? I mean in the end, you'll need access to the code in the container and if you docker-pull the container, you won't have access to the source code. I mean, it's easy enough to push the container but I was wondering what purpose that'd serve. |
@rednafi Got it!
Also, we could publish it to dockerhub if we want so anyone could pull the image for validating the working architecture. If someone chooses to use some container scheduler in the future, this someone would just need to track the container registry for having updates (Ex.: ArgoCD). |
I think you've convinced me. So, what I'll do is to push the container to GitHub registry and then see if anyone finds that useful. Thank you. |
After battling with the CI, this is now ready. Checkout the release for details. Thank you. |
What about a GitHub Action that publishes the Docker container to the GitHub repository registry?
The text was updated successfully, but these errors were encountered: