Explore >> Select a destination
|
You are here 
|
blog.alexellis.io | ||
| | | | |
nathanchance.dev
|
|
| | | | | Recently, I started exploring setting up a self-hosted GitHub Actions runner for the work-in-progress LLVM builds that ClangBuiltLinux is looking to distribute on kernel.org, as GitHub Actions hosted runners are pretty underwhelming in terms of performance and we want to soup these builds up with Profile Guided Optimization. Additionallly, GitHub Actions does not have a hosted arm64 Linux option, which is becoming increasingly important with chips such as Apple's M1 getting strong mainline Linux support. | |
| | | | |
blog.bytequalia.com
|
|
| | | | | Combining Kata Containers with Amazon EKS Distro provides secure VM workload isolation on the same secure Kubernetes distribution that runs on Amazon EKS. | |
| | | | |
actuated.dev
|
|
| | | | | GitHub doesn't provide hosted Arm runners, so how can you use native Arm runners safely & securely? | |
| | | | |
www.andrlik.org
|
|
| | | I've been using uv in my Github Actions workflows for a while now to speed up my runner environment creation, and I wanted to do the same for my publishing workflows. So, I created the following workflow for each of my PyPI packages. | ||
