Guides 11792 Published by Philipp Esselbach 0

On a brand‑new Ubuntu or Debian machine the article walks you through getting Gitea up and running, starting with a quick check of supported OS releases before updating packages and installing lightweight utilities like git, curl, wget, and unzip. It then creates a dedicated gitea user, downloads the latest single‑file binary, sets up proper directory ownership in /var/lib/gitea, and offers a choice between SQLite for simple use or MariaDB/PostgreSQL for production with SQL scripts to secure the database. Following that you configure app.ini, write a systemd unit that runs the web server under the gitea user, reload daemon files, enable and start the service, open port 3000 in UFW or firewalld, and finally access the web UI to finish setup through an account wizard. The guide also lists common pitfalls such as wrong architecture binaries, permission mishaps, and database connection errors, and ends with a friendly note that your new self‑hosted Git server is ready for teams, hooks, and code reviews.

Guides 11792 Published by Philipp Esselbach 0

An article walks you through three reliable ways to safely power down a Linux machine without pulling the plug. The first option, `shutdown -h now`, is a tried‑and‑true method that gracefully stops services and flushes buffers before halting; it’s best for servers needing a clean exit. If you’re on a minimal or misbehaving init system, `poweroff` offers a quicker bypass by sending a halt signal directly to the kernel, while `systemctl poweroff` lets systemd manage the shutdown process with logging and hooks. The guide also includes a handy table that maps each command to the appropriate scenario so you can choose the right one at a glance.

Guides 11792 Published by Philipp Esselbach 0

This guide shows how to secure SSH by allowing only specific users or groups, giving a quick‑fix for rogue accounts or abusive bots. Before making changes it tells you to back up sshd_config, keep an alternate session open, and check your OpenSSH version. It then explains the new UserAllow directive for OpenSSH 8.2+, the classic AllowUsers/DenyUsers syntax, and a group‑based Match block that lets you apply rules per environment. Finally it walks through reloading sshd without dropping existing connections, how to test the new rules with fresh logins or logs, and encourages choosing the method that matches your setup.

Guides 11792 Published by Philipp Esselbach 0

The guide explains how to quickly list every RPM installed on RHEL and CentOS machines using yum or dnf, so administrators can see the full stack after a fresh install or for audit purposes. It shows commands like “yum list installed” for RHEL 7 and CentOS 7, switching to “dnf list installed” on newer releases, and also offers filtering options with grep or dnf repoquery to narrow down by package name or repository source. For compliance work the article suggests redirecting the output into a text file so you can later compare snapshots or import the data into spreadsheets for sorting. Finally it highlights quick checks such as “rpm -q curl” and gives a real‑world example where missing httpd modules caused service outages, illustrating how to troubleshoot with these tools.

Guides 11792 Published by Philipp Esselbach 0

This guide walks you through setting up automated security updates on CentOS 8 and Rocky Linux 8 using dnf-automatic, explaining why automation matters for keeping systems patched without manual intervention. It covers installing the daemon, editing /etc/dnf/automatic.conf to limit upgrades to security fixes, configuring random sleep delays, customizing the systemd timer with OnCalendar entries, and enabling the service. The tutorial also shows how to test the timer, receive email alerts when updates are available but not applied, clean the package cache, and share real‑world lessons about avoiding synchronized spikes and kernel regressions. Finally, it offers practical best practices such as testing on staging, monitoring logs in /var/log/dnf.log, keeping backup snapshots, and emphasizes that with these steps your machine stays protected while you only need to check the logs if something goes wrong.