/explore
|
You are here 
|
blog.oddbit.com | ||
| | | | |
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. | |
| | | | |
billglover.me
|
|
| | | | | Docker has had the ability to build multi-architecture images for a while. I've never had cause to use it, until now. In this post I'll walk through building a docker image that should work on your laptop and a Raspberry Pi. | |
| | | | |
actuated.dev
|
|
| | | | | QEMU is a convenient way to publish containers for multiple architectures, but it can be incredibly slow. Native is much faster. | |
| | | | |
chipx86.blog
|
|
| | | Here's a very quick, not exactly comprehensive tutorial on building Docker images using multiple hosts (useful for building multiple architectures). If you're an expert on docker buildx, you may know all of this already, but if you're not, hopefully you find this useful. We'll make some assumptions in this tutorial: We want to build a... | ||
