Explore >> Select a destination
|
You are here 
|
calyptia.com | ||
| | | | |
blog.alexellis.io
|
|
| | | | | I saw an opportunity to fix self-hosted runners for GitHub Actions. Actuated is now in pilot and aims to solve most if not all of the friction. | |
| | | | |
actuated.com
|
|
| | | | | GitHub warns against using self-hosted Actions runners for public repositories - but why? And are there alternatives? | |
| | | | |
blog.oddbit.com
|
|
| | | | | At work we have a cluster of IBM Power 9 systems running OpenShift. The problem with this environment is that nobody runs Power 9 on their desktop, and Docker Hub only offers automatic build support for the x86 architecture. This means there's no convenient options for building Power 9 Docker images...or so I thought. It turns out that Docker provides GitHub actions that make the process of producing multi-architecture images quite simple. | |
| | | | |
davquar.it
|
|
| | | A GitHub Action is the automatic execution of a job, after a specified trigger on a GitHub repository. For example, let's say that we want to run a linter on each new commit, we can create a GitHub action to do it. In this post we'll see a workflow to automatically deploy a Hugo site on GitHub Pages. | ||
