Skip to content

Blog

In this section you will find articles write mainly during research sessions.

Power consumption

With this beautiful monitoring stack and all the effort I put on the system optimisation to make the homelab power efficient, it is a nice feature to monitor the power draw from the wall.

Fail2Ban installation and setup

Fail2Ban scans log files like /var/log/auth.log and bans IP addresses conducting too many failed login attempts. It does this by updating system firewall rules to reject new connections from those IP addresses, for a configurable amount of time. Fail2Ban comes out-of-the-box ready to read many standard log files, such as those for sshd and Apache, and is easily configured to read any log file of your choosing, for any error you wish.

Monitoring

Setting up a monitoring stack for a homelab is critical to ensuring optimal performance, reliability, and security. It allows you to track resource usage, perform health checks, and troubleshoot problems issues, minimizing downtime. Overall, a robust monitoring setup is essential for maintaining a well-functioning and efficient homelab.

Hardware overview

This article explores the hardware of a scalable hosting service that use Docker Swarm for efficient container orchestration and a lot of storage for centralized data management. It evaluates various hardware options, including servers, networking equipment, and storage solutions.

Container orchestration

In a homelab environment, selecting the most suitable container orchestration tool is crucial for optimizing experimentation and management.
This article compares Docker Compose, Docker Swarm, Kubernetes light distribution (like K0S and Minikube), and Kubernetes to identify the best fit for my use case. Docker Compose simplifies multi-container setups while Docker Swarm provides straightforward clustering and scaling, and K0S and Minikube offer lightweight Kubernetes experiences for testing and learning.