Guides 11795 Published by Philipp Esselbach 0

The guide walks you through installing Navidrome on Debian 11 by first ensuring you have ffmpeg, enough free disk space, and root or sudo access, then adding the official repository and pulling the binary with apt. It explains how to edit the systemd unit so the service runs as www‑data, points ND_MUSICFOLDER to your music directory, selects a port, and optionally adds a hosts entry for local DNS resolution. After enabling and starting the service you can check that it’s running, review logs if it fails, and reach the web UI at http://:4533 or http://music.local:4533 to create an admin account. The author also suggests optional tweaks like using an SSL reverse proxy, adjusting file permissions, setting up auto‑updates, and shares practical lessons about permission errors and a full /var directory that can kill the service.

Guides 11795 Published by Philipp Esselbach 0

The guide explains how to install balenaEtcher on Fedora 36 by using Flatpak, which bundles all required dependencies and avoids the broken official RPM that expects an older glibc. It walks through enabling Flathub, installing the Etcher flatpak package, and launching it—granting the necessary permission to access removable drives when prompted. An alternative method is also provided: downloading and running the AppImage directly, though you’ll still need to authenticate for flashing. Finally, the article notes common issues such as permission errors or USB detection problems and shows how to resolve them, plus a reminder to keep Etcher updated via flatpak update.

Guides 11795 Published by Philipp Esselbach 0

The guide explains how to install Fedora 36’s built‑in Cockpit package with a simple dnf install cockpit command and then activate its systemd socket using systemctl enable --now cockpit.socket, which makes the web console start on demand. It shows how to open port 9090 through firewalld by adding the “cockpit” service permanently and reloading the firewall, ensuring remote browsers can reach the interface. A quick verification step with systemctl status cockpit.socket confirms that the socket is active and listening on all interfaces. Finally, you access Cockpit at https://<your‑fedora‑ip>:9090, accepting the self‑signed certificate and logging in with your existing PAM credentials.

Guides 11795 Published by Philipp Esselbach 0

The passage is a step‑by‑step guide for installing the newer Linux 5.17 kernel on an AlmaLinux 8 system while preserving the older 5.4 LTS kernel as a fallback. It explains why a newer kernel may be required (e.g., hardware compatibility issues) and shows how to add the ELREPO repository, enable its kernel sub‑repo, and install the mainline kernel‑ml package via dnf. The tutorial also covers verifying the GRUB entry, optionally installing the 5.4 kernel from the archive, cleaning up unused kernels, and rebooting to confirm the new version is active. Finally, it emphasizes that you can always select the older kernel at boot if any problems arise.

Guides 11795 Published by Philipp Esselbach 0

The article explains how enabling GZIP compression in Nginx can dramatically reduce the size of HTML, CSS, and JavaScript files, leading to faster page loads on slow connections and lower bounce rates. It walks through locating the correct configuration file, inserting directives such as `gzip on;`, `gzip_vary on;`, `gzip_proxied any;`, `gzip_comp_level 6;` and specifying common MIME types while noting that overly aggressive compression can waste CPU resources. The author demonstrates how to test the setup with `nginx -t`, reload the service without downtime, and verify that responses are compressed using curl or browser dev‑tools. Finally, practical cautions about already‑compressed assets, header overhead, CDN compatibility, and a quick FAQ help readers avoid common pitfalls and decide when GZIP is appropriate.

Guides 11795 Published by Philipp Esselbach 0

The article explains how to install a newer version of Nginx on Ubuntu 20.04 by either using the default Ubuntu package (stable 1.18) for a quick, “good‑enough” setup or adding the official nginx.org repository to obtain the latest stable (≈1.22) or mainline (≈1.23) releases with extra features. It walks through adding the signing key, creating separate source‑list files for each branch, updating the package index, installing Nginx, verifying the service, and safely rolling back to the Ubuntu version if needed. Throughout, it emphasizes choosing the appropriate branch based on risk tolerance—stable for production stability and mainline for cutting‑edge functionality.

Guides 11795 Published by Philipp Esselbach 0

The passage explains three methods for installing OpenJDK 11 on Ubuntu 20.04—using the official Ubuntu repository, adding a trusted PPA, or manually extracting a tar.gz archive. It outlines step‑by‑step commands for each approach and notes that the repo install offers stability, the PPA provides newer patches at the cost of added trust, and the manual method gives full control but requires self‑managed updates. Additionally, it emphasizes verifying the installation with java -version and cautions about potential incompatibilities when using unofficial PPAs. Finally, it advises readers to choose the method that best matches their update preferences and maintenance comfort level.

Guides 11795 Published by Philipp Esselbach 0

The guide explains how to install Telegram Desktop on Fedora 36 using either a native RPM package or a Flatpak from Flathub. The first method updates the system with dnf update and then installs the officially maintained telegram-desktop package, after which the app can be launched from the menu or command line. The second method ensures you get the newest upstream version by installing Flatpak (if needed), adding the Flathub repository, and pulling the Telegram flatpak with a single non‑interactive command, then running it via flatpak run. It also notes how to keep each installation up‑to‑date—using dnf upgrade telegram-desktop for the RPM or simply running flatpak update for the sandboxed version.

Guides 11795 Published by Philipp Esselbach 0

The guide shows two fast ways to install Telegram Desktop on Fedora 36: a simple DNF installation of the distro‑provided telegram-desktop RPM and a Flatpak pull from Flathub for the newest upstream build. The DNF method updates the repository metadata first, installs the telegram-desktop package, and can be kept current with regular dnf upgrade telegram-desktop. The Flatpak method ensures up‑to‑date software by installing Flatpak (if needed), adding the Flathub remote, then installing and running org.telegram.desktop, which bundles its own libraries to avoid missing‑dependency issues. Both approaches finish with a short tip on how to keep each version updated—using dnf upgrade for the RPM or flatpak update for the sandboxed build.