Explore >> Select a destination
|
You are here 
|
actuated.dev | ||
| | | | |
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. | |
| | | | |
inlets.dev
|
|
| | | | | On Nov 1st, all images pulled from the Docker Hub will be subjected to severe limits, which will affect all Kubernetes users. Learn what solutions exist, and how how to prepare. | |
| | | | |
wittchen.io
|
|
| | | | | Recently GitHub introduced really interesting feature to their service called Actions. Actions can be used for automating various tasks related to the repositories like CI, CD, testing, deployment and whatnot. The general concept is as follows: We can create so called action, which can be based on a JavaScript project or a Docker container. We can also use existing actions in the Marketplace. Next, we can create workflow in the yml file, where we define our workflow. Workflow can consist of on a job with many steps using different actions. We can also define multiple jobs, where one depends on another. Workflows can be triggered in many ways. E.g. by push, pull request, creating issue, publishing release, scheduled event or external event. | |
| | | | |
conductofcode.io
|
|
| | | I set out to learn about Azure Functions and this is the knowledge I have gathered so far. | ||
