ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
AlmaLinux keeps RHEL binary compatibility for the OS base and uses AppStream dnf modules to isolate application versions. This lets you run certified workloads while choosing specific language streams without upgrading the entire system.
On Rocky Linux 8 and 9, DNF module streams let you pin a major version like Node.js 18 from AppStream instead of adding third-party repos. Choose the stream first, install, and verify.
Learn how to use Rocky Linux’s DNF module system to pick specific application versions, keep your OS stable, and manage side‑by‑side deployments. A step‑by‑step guide with real commands, trade‑offs, and a concrete PostgreSQL example.
Context AlmaLinux 9 ships dnf module streams for language runtimes such as Node.js, Python, and Go, allowing version selection via dnf module install nodejs:18 . Switching streams requires dnf module reset followed by dnf module enable , a non‑transactional sequence that can leave orphaned packages or unresolved dependencies. The AlmaLinux Build System publi
Goal I want a reliable way to detect, before patching or provisioning, whether any enabled AppStream module stream on an AlmaLinux 9 system has passed its end-of-life date, so I can plan a stream switch before security updates stop. Constraints and uncertainty From what I understand, only one stream per module can be enabled at a time, and an EOL stream rema
rockylinux
podman