You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can you deploy an action under the denyhosts/denyhosts-sync-docker repo to deploy the Docker Container automatically over to Docker? I took a quick glance at doing it but figured you might be better doing it than myself. Being that I'm not as well versed in Docker as you are.
The text was updated successfully, but these errors were encountered:
hmmmm, I've never used actions before, don't think there was a docker one when I set it all up.
I've always just used the "Automated Builds" within Docker hub, which automalily triggers a new build when a change is made in GitHub.
I'll have a look at what Github actions adds when I've got a sec free.
Looking at the actions that I committed, it seems that the action will run a test and build the image, and then commit the resulting image to Packages on GitHub. I was able to setup on Docker to do builds when github PR's are merged to master.
I'm thinking that with Actions, we can check if the denyhosts or denyhosts-sync repos have been updated. Then if they'ved been updated, that a new docker version is triggered to be built. Pretty sure I saw that a build trigger can be invoked on docker by accessing a generated URL.
Can you deploy an action under the denyhosts/denyhosts-sync-docker repo to deploy the Docker Container automatically over to Docker? I took a quick glance at doing it but figured you might be better doing it than myself. Being that I'm not as well versed in Docker as you are.
The text was updated successfully, but these errors were encountered: