Six FOSS Tutorials Worth Reading This Autumn
Every week the open-source world publishes a pile of tutorials, and a fair number of them are better than the official documentation they sit next to. The trick is finding the ones that name a version, show the command, and admit what still does not work.
These six guides were published between mid-September and mid-October 2026, and each one closes a gap that most write-ups leave open. They cover Cloudflare’s new command line tool, running your own Git forge, a music server that behaves itself on SELinux, the console change coming in Fedora 45, local AI for your paperwork, and a hardware key that will not lock you out of your own machine.
1. Flavio Copes: using the new Cloudflare cf CLI
Cloudflare announced cf as an open beta on 28 September 2026, and it is intended to replace Wrangler. Rather than hand-writing commands, cf generates them from the OpenAPI schema behind the Cloudflare API, which is how it arrives with more than 2,900 of them and consistent names across products that used to disagree.
Copes walks through the parts that matter on day one: cf cli search when you know the task but not the command, cf auth login for the one-time sign-in, and cf init to scaffold a Worker whose configuration now lives in cloudflare.config.ts instead of wrangler.jsonc. Results are JSON by default, so the usual --json flag juggling with Wrangler goes away.
The two warnings are worth the click on their own. A delete that you decline to confirm prints “Aborted” and still exits with status 0, so a naive script will not notice that nothing happened. And live logs plus single-secret uploads still need Wrangler, so this is not yet a clean swap.
Read it: How to use cf, the new Cloudflare CLI
2. jacar.es: Forgejo behind Caddy, with a runner attached
Forgejo is the community-governed fork of Gitea, and if you have been meaning to move your repositories onto hardware you control, this is the guide to start with. It was written against Forgejo 16 on an arm64 machine, and it publishes the compose file the author actually ran rather than a cleaned-up sketch.
The detail that saves an afternoon: since 16.0 the container no longer trusts every reverse proxy. Unless REVERSE_PROXY_TRUSTED_PROXIES is set to Caddy’s IP, your logs record the proxy address instead of the real client. That is why the compose file gives the network a fixed subnet. The runner has to reach Forgejo through its public URL as well — pointing it at the internal http://forgejo:3000 makes the first workflow fail at the clone step.
It also opens with the reason to upgrade: 16.0.4 and the LTS 15.0.8 shipped on 10 September 2026 to fix a critical remote code execution flaw in repository creation from templates (CVE-2026-89094, CVSS 9.9). The 16.0 branch stops receiving support on 29 October 2026, so the LTS branch is the safer long-term bet.
Forgejo is in our directory: Forgejo. Read the guide: Install Forgejo with Docker, Caddy and Runner
3. Fedora Magazine: Navidrome in Podman, SELinux included
Navidrome is the open-source answer to “I would like my own Spotify”: it indexes a music folder and streams it to any browser or Subsonic client. The Fedora guide installs it with Podman, and unlike most container write-ups it does not skip SELinux.
The two commands people forget are semanage fcontext -a -t container_file_t on the data and music directories, followed by restorecon -R on both. Without them the container simply cannot read your library. The guide then runs the container as your own UID and GID rather than root, mounts the music directory read-only, and publishes port 4533.
Official images exist for amd64, arm64 and arm/v6-v7, so a Raspberry Pi is a perfectly good host. If you want the container managed by systemd instead of a compose file, our Podman listing covers the basics, and Navidrome is in the directory too.
Read it: Installing Navidrome on Fedora Linux using Podman
4. Fedora Magazine: what kmscon changes about the Linux console
Fedora 45 replaces the kernel’s fbcon driver with kmscon, a userspace console, on tty1 through tty6. If you work in a text-only session, or you maintain scripts that assume /dev/tty1, read this before you upgrade.
The reasoning is sound. fbcon bugs run in kernel space, where a crash is a kernel panic. It only understands bitmap fonts, which is painful on a HiDPI laptop. And it lost scrolling to a CVE. kmscon renders with freetype, follows the keyboard layout you set with localectl, and talks to the GPU through DRM.
The practical changes are what make the article worth keeping: tty now reports /dev/pts/0 rather than /dev/tty1, setfont and loadkeys no longer do anything, and a program that wants the GPU has to ask kmscon to release it first with kmscon-launch-gui.
Read it: Modernizing the console with kmscon
5. wz-it: Paperless-ngx with local AI, no cloud in the loop
Paperless-ngx has shipped its own AI since 3.0.0 on 22 July 2026: suggestions for title, tags, correspondent and document type, a chat about a single document or the whole archive, and a vector index for finding similar paperwork. Version 3.1.0 added a workflow action that applies those suggestions automatically.
What this guide does well is the wiring. Everything is off by default behind PAPERLESS_AI_ENABLED=false, the language model can point at a local Ollama server, and so can the embeddings, which keeps the archive on your own hardware. It also documents the migration path, and that matters: the separate Paperless-AI project has carried an unmaintained notice since March 2026, so bolting that onto a new install is no longer the sensible route.
Every detail is pinned to 3.3.0, released 6 October 2026, which is the version to install. Paperless-ngx is in our directory.
Read it: Paperless-ngx 3 AI Setup: Native AI (v3.3) with Local Ollama
6. EGLUG: a YubiKey for SSH and sudo, without locking yourself out
Hardware keys are the least glamorous upgrade you can make to a workstation, and this walkthrough is the one I would hand to somebody who has never used one. It covers setting the FIDO2 PIN with ykman, generating a resident ed25519-sk key whose private half never leaves the device, and wiring pam_u2f into sudo.
The troubleshooting section is why it earns a place here. It deals with the failures that actually happen: no prompt appearing when you run sudo, the key working locally but not over SSH, and getting locked out after switching sudo to two factors. Testing in a second terminal before you close the first is the whole ballgame.
You need OpenSSH 8.2 or newer and a key with FIDO2 support, meaning the 5 Series, the Security Key Series or the Bio. Package names differ by distribution, and the guide lists them for Debian, Fedora and Arch.
Read it: How to Set Up a YubiKey for SSH and Sudo on Linux
What all six have in common
Three things, and they are the reason these six made the cut rather than the dozens of other tutorials published in the same weeks.
- They name versions. Forgejo 16.0.4, Paperless-ngx 3.3.0, OpenSSH 8.2, Fedora 45. You can tell whether a guide still applies to your machine.
- They show the command, not just the concept. Every section above contains something you can paste, and each guide explains what the flags do.
- They document the failure mode. An exit code that lies, a proxy that swallows the client address, a filesystem context that blocks the container, a console change that breaks your scripts. That is the part documentation usually skips.
The bottom line
If you only have one evening, start with Forgejo: it replaces a service you probably rent, and the guide is honest about the bits that break. If you have ten minutes and a laptop you care about, do the YubiKey one — it is the largest security gain per minute of work in this list.
For the rest, take them in the order your own to-do list suggests. The cf CLI guide matters only once you touch Workers, kmscon only matters if you upgrade to Fedora 45, and the Paperless-ngx piece only matters if you already keep a document archive. But when each of those days arrives, it is good to know the guide already exists.
Looking for more tools? Browse the full directory for free and open source software, or start with self-hosted apps and CLI and terminal tools.