# Alex Ellis' Blog OSS, Cloud Native & Raspberry Pi This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## How and Why We Bought 4x DGX Sparks DevFeed: [How and Why We Bought 4x DGX Sparks]() Original publisher: [Read original article]() Author: Alex Ellis Published: 2026-09-15T00:00:00Z Content type: opinion Language: en Sources: [Alex Ellis' Blog]() Topics: [Local AI](), [GPU](), [qwen](), [Cloud]() Tags: [agents](), [ai](), [cloud](), [gpu](), [llm](), [local-ai](), [localai](), [qwen](), [red-teaming](), [security]() ### AI overview The author explains why OpenFaaS Ltd bought four DGX Sparks and what the team learned from deploying local AI. The article argues that local infrastructure can provide tangible privacy and risk-reduction benefits for business use cases, even though it is not primarily justified by cost per token. ### Source excerpt In June we deployed an RTX 6000 Pro into production, a few weeks later, we're now operating DGX Sparks for the team. Learn how and why. ## Local Qwen isn't a worse Opus, it's a different tool DevFeed: [Local Qwen isn't a worse Opus, it's a different tool]() Original publisher: [Read original article]() Author: Alex Ellis Published: 2026-06-17T00:00:00Z Content type: opinion Language: en Sources: [Alex Ellis' Blog]() Topics: [qwen](), [Claude](), [Artificial Intelligence]() Tags: [agents](), [ai](), [ai-tools](), [claude](), [gpu](), [llm](), [localai](), [qwen](), [source]() ### AI overview The author shares a founder's experience using local Qwen models in a small software business and open source projects. The models have provided useful, specific value, but the author still does not trust them unsupervised because of infinite loops and hallucination risks, especially after quantization for a consumer GPU. ### Source excerpt We've all heard people say that Qwen is near-Opus level, but I have receipts and am here to be transparent with you. ## I wrote a replacement for GitHub's code review bot DevFeed: [I wrote a replacement for GitHub's code review bot]() Original publisher: [Read original article]() Author: Alex Ellis Published: 2025-11-18T00:00:00Z Content type: opinion Language: en Sources: [Alex Ellis' Blog]() Topics: [GitHub](), [Code review](), [GitHub Copilot code review](), [Pull Request]() Tags: [agent](), [code-review](), [firecracker](), [github](), [github-copilot](), [large-language-models-llms](), [linux](), [llm](), [opencode](), [review](), [self-hosted](), [self-hosting](), [slicer](), [source]() ### AI overview The author describes building a replacement for GitHub's code review bot. They explain code review bots and compare GitHub Copilot's feedback with the opencode CLI, reporting that Copilot's feedback was superficial while opencode produced more useful review feedback for an OpenFaaS product change. ### Source excerpt If GitHub themselves have a native code review bot, why not just use it? ## Preview: Slice Up Bare-Metal with Slicer DevFeed: [Preview: Slice Up Bare-Metal with Slicer]() Original publisher: [Read original article]() Author: Alex Ellis Published: 2025-08-30T08:09:48Z Content type: release Language: en Sources: [Alex Ellis' Blog]() Topics: [Firecracker](), [Kubernetes](), [OpenFaaS](), [systemd](), [Arch Linux](), [Arm](), [migration](), [Ollama]() Tags: [arm](), [bare-metal](), [boot](), [deploy](), [firecracker](), [k3s](), [kubernetes](), [linux](), [network](), [preview](), [self-hosting](), [slicer](), [storage](), [systemd](), [testing](), [work](), [x86-64]() ### AI overview OpenFaaS Ltd is previewing Slicer, an internal tool that partitions bare-metal hosts into Firecracker microVMs. The article describes use cases including Kubernetes cluster scaling, customer simulations, chaos testing, production troubleshooting, Arm and x86_64 testing, persistent workloads, multi-host deployments, and GPU access for Ollama. ### Source excerpt The easiest and best supported way to learn and deploy Firecracker and microVMs. ## Intel N100 Mini PC for R&D and Self-Hosting Compared with Raspberry Pi 5 DevFeed: [Intel N100 Mini PC for R&D and Self-Hosting Compared with Raspberry Pi 5]() Original publisher: [Read original article]() Author: Alex Ellis Published: 2025-08-18T08:09:48Z Content type: opinion Language: en Sources: [Alex Ellis' Blog]() Topics: [pc](), [intel](), [cpu](), [Self-hosted](), [Raspberry Pi](), [NVMe](), [Firecracker](), [Kubernetes](), [Linux](), [k3s](), [OpenFaaS](), [ddr5]() Tags: [ddr5](), [firecracker](), [github-actions](), [intel](), [k3s](), [kubernetes](), [linux](), [m-2-nvme](), [mini-pc](), [pc](), [processor](), [self-hosting](), [storage](), [threads](), [work]() ### AI overview The article evaluates the low-power Intel N100 Mini PC for R&D and self-hosting, comparing it with the Raspberry Pi 5. It discusses CPU, RAM, NVMe storage, Ethernet, virtualization, Kubernetes, Firecracker, and cost considerations. ### Source excerpt Exploring the capabilities of the Intel N100 Mini PC for work and self-hosting as an alternative to public cloud. ## The 90s UNIX Utility That Fell Out of Favour DevFeed: [The 90s UNIX Utility That Fell Out of Favour]() Original publisher: [Read original article]() Author: Alex Ellis Published: 2025-08-15T08:09:48Z Content type: opinion Language: en Sources: [Alex Ellis' Blog]() Topics: [Unix](), [Linux](), [macOS](), [Bash]() Tags: [bash](), [linux](), [macos](), [network](), [remote-access](), [terminal](), [unix]() ### AI overview An essay revisits the UNIX finger utility, explaining its origins in a high-trust environment where it exposed user information such as login status, idle time, phone numbers, and email activity. It also reflects on the author's early experiences with Linux, MUD servers, telnet, and bash. ### Source excerpt I reminisce of the days of i386, Slackware Linux, and forgotten plaintext UNIX utilities that are still on modern Macs today. ## How to run Firecracker without KVM on cloud VMs DevFeed: [How to run Firecracker without KVM on cloud VMs]() Original publisher: [Read original article]() Author: Alex Ellis Published: 2025-02-12T09:05:21Z Content type: tutorial Language: en Sources: [Alex Ellis' Blog]() Topics: [Firecracker](), [virtualization](), [virtual machines](), [Cloud](), [Amazon Web Services](), [Amazon EC2]() Tags: [aws](), [bare-metal](), [cloud](), [ec2](), [firecracker](), [github-actions](), [kvm](), [qemu](), [virtual-machines](), [virtualization]() ### AI overview This tutorial introduces a way to run microVMs on cloud virtual machines without KVM, using the PVM virtualization framework. It explains the limitations of nested virtualization and compares the cost of AWS bare-metal EC2 with alternatives. ### Source excerpt MicroVMs need bare-metal or nested virtualisation with /dev/kvm. But what if that's not available? The PVM virtualisation framework may be the answer. ## Using a Portable Monitor for Home-Lab Debugging and Streaming DevFeed: [Using a Portable Monitor for Home-Lab Debugging and Streaming]() Original publisher: [Read original article]() Author: Alex Ellis Published: 2024-06-12T13:47:26Z Content type: opinion Language: en Sources: [Alex Ellis' Blog]() Topics: [Homelab](), [monitor](), [Raspberry Pi](), [Jenkins](), [Tooling](), [ci]() Tags: [ci](), [debugging](), [headless](), [home-lab](), [jenkins](), [portable](), [raspberry-pi](), [video]() ### AI overview The article explains why the author prefers a portable monitor for debugging headless home-lab computers, setting up Raspberry Pis, monitoring Jenkins CI pipelines, and managing streaming or product-demo software. ### Source excerpt I cover why as a one monitor kind of guy, I found a portable monitor essential - both for streaming and for debugging the home lab. ## Explore and debug GitHub Actions via SSH DevFeed: [Explore and debug GitHub Actions via SSH]() Original publisher: [Read original article]() Author: Alex Ellis Published: 2024-02-20T11:47:47Z Content type: tutorial Language: en Sources: [Alex Ellis' Blog]() Topics: [GitHub Actions](), [ssh](), [OpenSSH](), [Command-line interface](), [nginx](), [web applications]() Tags: [cli](), [debug](), [debugging](), [gateway](), [github](), [github-actions](), [ssh](), [tcp](), [troubleshooting]() ### AI overview This tutorial explains how to use the actuated SSH gateway to access hosted or self-hosted GitHub Actions runners for debugging and exploration. It covers ephemeral shells, troubleshooting jobs, port forwarding, and copying files. ### Source excerpt As part of actuated, we needed to debug and explore VM images for GitHub Actions via SSH. I'm now making that available to my GitHub Sponsors for free. ## Booting the Raspberry Pi 5 from NVMe DevFeed: [Booting the Raspberry Pi 5 from NVMe]() Original publisher: [Read original article]() Author: Alex Ellis Published: 2023-12-28T17:55:43Z Content type: tutorial Language: en Sources: [Alex Ellis' Blog]() Topics: [NVMe](), [Raspberry Pi](), [boot](), [Linux](), [pcie](), [Ethernet](), [Edge](), [Google](), [Machine learning]() Tags: [boot](), [edge](), [ethernet](), [google](), [hdmi](), [linux](), [ml](), [mount](), [network](), [nvme](), [pcie](), [raspberry-pi](), [raspberry-pi-5](), [raspberry-pi-os]() ### AI overview A practical workflow for configuring a Raspberry Pi 5 to boot Raspberry Pi OS from NVMe for headless use. The article discusses first-generation PCIe breakout boards, recommends flashing a fresh image instead of cloning a booted SD card, and outlines setup steps using Ethernet, HDMI, or network scanning. ### Source excerpt Here's my workflow for setting up the Raspberry Pi 5 to boot from NVMe for headless use. ## GitHub Actions as a time-sharing supercomputer DevFeed: [GitHub Actions as a time-sharing supercomputer]() Original publisher: [Read original article]() Author: Alex Ellis Published: 2023-12-22T12:23:04Z Content type: tutorial Language: en Sources: [Alex Ellis' Blog]() Topics: [GitHub Actions](), [GitHub](), [Bash](), [Command-line interface](), [Open Source](), [Linux Kernel]() Tags: [automation](), [bash](), [batch](), [cli](), [github](), [github-actions](), [linux-kernel](), [open-source]() ### AI overview The article presents actions-batch, an open-source CLI that uses GitHub Actions workflows to run local Bash jobs in a repository and retrieve their outputs. It frames this as an unofficial time-sharing system for executing batch jobs, with support for secrets and self-hosted runners. ### Source excerpt Learn how and why I turned GitHub's APIs into a time-sharing supercomputer from the 1970s to execute modern batch jobs. ## First Impressions with the Raspberry Pi 5 DevFeed: [First Impressions with the Raspberry Pi 5]() Original publisher: [Read original article]() Author: Alex Ellis Published: 2023-09-28T10:55:07Z Content type: opinion Language: en Sources: [Alex Ellis' Blog]() Topics: [Raspberry Pi](), [Self-hosted](), [Kubernetes](), [GitHub Actions](), [Firecracker]() Tags: [bare-metal](), [benchmarking](), [raspberrypi](), [servers]() ### AI overview An early, server-focused first-impressions article on the Raspberry Pi 5. The author discusses its PCIe port and potential use for self-hosted servers, Kubernetes clusters, and isolated CI runners. ### Source excerpt For someone who runs the Raspberry Pi as a server, build agent and for Kubernetes, how does the new version stack up? And should you upgrade? ## Configuring Kubernetes Pods to Trust Self-Signed Certificates DevFeed: [Configuring Kubernetes Pods to Trust Self-Signed Certificates]() Original publisher: [Read original article]() Author: Alex Ellis Published: 2023-06-27T11:09:18Z Content type: tutorial Language: en Sources: [Alex Ellis' Blog]() Topics: [certificates](), [Kubernetes](), [TLS (Transport Layer Security)]() Tags: [certificates](), [helm](), [kubernetes](), [tls]() ### AI overview The article discusses ways for Kubernetes workloads to trust self-signed certificates or a custom certificate authority without bypassing TLS verification. It covers application-level trust-bundle loading and supplying certificate bundles through mounted volumes in deployment configuration. ### Source excerpt Self-signed certificates are common within enterprise companies. But how do you distribute them and enable their use in Kubernetes as a user and a vendor? ## How to use multiple Docker registry mirrors DevFeed: [How to use multiple Docker registry mirrors]() Original publisher: [Read original article]() Author: Alex Ellis Published: 2023-06-08T13:27:06Z Content type: tutorial Language: en Sources: [Alex Ellis' Blog]() Topics: [Docker](), [docker registry](), [pull through cache](), [Self-hosted](), [GitHub Actions](), [Firecracker]() Tags: [buildx](), [cache](), [container](), [container-registry](), [docker](), [docker-registry](), [firecracker](), [github-actions](), [how-to](), [kubernetes](), [linux](), [mirror](), [registries](), [registry](), [self-hosted]() ### AI overview This tutorial explains why self-hosted GitHub Actions runners can hit Docker Hub's anonymous image pull limits and how a Docker registry configured as a pull-through cache can help. It covers configuring Docker and buildx to use multiple registry mirrors, including considerations for local HTTP and Internet-facing HTTPS setups. ### Source excerpt Why would you need to use a mirror for a container registry? And is there a way to use two or more? Find out from the actuated team. ## Docker requires some organisation accounts to upgrade to a paid plan or lose their images DevFeed: [Docker requires some organisation accounts to upgrade to a paid plan or lose their images]() Original publisher: [Read original article]() Author: Alex Ellis Published: 2023-03-15T10:56:54Z Content type: opinion Language: en Sources: [Alex Ellis' Blog]() Topics: [Docker Hub](), [Open Source](), [Maintainers](), [Docker]() Tags: [community](), [cost](), [docker](), [docker-hub](), [github](), [maintainers](), [open-source](), [opinion]() ### AI overview The article discusses Docker's notice that some Docker Hub organisation accounts must upgrade to a paid team plan or risk deletion of the account and its images. It says the change affects organisation accounts used by open-source communities, while personal accounts were unchanged, and criticizes Docker's communication and cost. ### Source excerpt This controversial decision coupled with poor messaging has created anxiety the Open Source community. Learn what's happening and how we can move forward.