DEV Community: Giorgi Anakidze

Proxmox Post‑Install Configuration (Save Time & Resources)

Giorgi Anakidze — Tue, 05 Aug 2025 06:47:31 +0000

Proxmox Post‑Install Configuration

Installing Proxmox is straightforward, but a few tweaks right after installation can make it faster, more reliable, and lighter on resources — especially for homelabs.

Quick Wins After Installation

📧 Set a real admin email → Use it for system alerts & backups
🌐 Assign a static IP → Avoid losing access when DHCP changes
🛠 Run a post‑install script → Automate updates, disable nag screens, and clean up defaults
⚡ Disable unused services → e.g., High Availability on single‑node setups

These small changes:

Improve your day‑to‑day Proxmox experience
Prevent future network headaches
Save system resources on smaller homelab servers

💡 In the full guide, I cover:

Running the Proxmox post‑install script step‑by‑step
Disabling the Enterprise repo for community edition
Turning off unnecessary services like HA
Recommended network and email alert configurations

👉 Read the full tutorial here:

Proxmox Post‑Install Configuration

💬 What’s the first thing you change after installing Proxmox? Share your setup in the comments!

Cloud‑Init Your Proxmox Homelab VMs (Save Time & Disk Space)

Giorgi Anakidze — Mon, 04 Aug 2025 07:40:29 +0000

Cloud‑Init Your Proxmox Homelab VMs

Still creating full VMs manually in Proxmox? Cloud‑Init can save time and disk space by letting you configure a VM once and clone it instantly — with users, SSH keys, and networking already set up.

With Cloud‑Init you can:

⚡ Deploy new VMs in seconds
💾 Save storage with linked clones
🔑 Pre‑configure SSH, DNS, and networking
🛠 Keep all VMs consistent without manual setup

Why It Matters

Cloud‑Init is perfect for:

Homelabs with multiple VMs
Rebuilding or scaling quickly
Avoiding repetitive configuration

💡 In the full guide, I cover:

Downloading & preparing a Cloud‑Init image for Proxmox
Setting up a VM template with Cloud‑Init properties
Full vs Linked clones explained
Enabling password or SSH key access
Automating network setup

👉 Read the full tutorial here:

Cloud‑Init Your Proxmox Homelab VMs

💬 Have you switched your Proxmox VMs to Cloud‑Init yet? Share your experience in the comments!

Easy SSL Certificates for Your Homelab Services (Using Nginx Proxy Manager & Cloudflare)

Giorgi Anakidze — Sun, 03 Aug 2025 11:48:48 +0000

Easy SSL Certificates for Your Homelab Services

Tired of those annoying browser SSL warnings when accessing your homelab services?

With the right setup, you can have free HTTPS certificates for all your self-hosted apps — even if they run only on your local network.

Using Nginx Proxy Manager with Let’s Encrypt and a DNS challenge via Cloudflare, you can:

🔒 Secure every service in your homelab with HTTPS
🌍 Access services via friendly domain names (no more IPs!)
🚀 Automate certificate renewal without touching each service

Why This Matters

Better security → Encrypted connections, even on local network
No SSL warning popups → Clean experience on all devices
Easier access → Use proxmox.example.com instead of 192.168.1.50:8006

💡 In the full guide, I cover:

Installing Nginx Proxy Manager on Proxmox
Setting up a wildcard SSL certificate with Let’s Encrypt
Configuring Cloudflare API tokens for DNS challenge
Mapping your homelab services to friendly domain names
Forcing SSL + enabling HTTP/2 for better performance

👉 Read the full tutorial here:

Easy SSL Certificates for Your Homelab Services

💬 How are you currently securing your homelab services? Share your setup in the comments!

Intro to Message Brokers in Microservices (RabbitMQ & Kafka)

Giorgi Anakidze — Sat, 02 Aug 2025 08:56:59 +0000

Message Brokers for Microservices: RabbitMQ, Kafka & Real Examples

In modern microservices, reliable communication between services is critical — especially when dealing with failures, scaling, and asynchronous workflows. That’s where message brokers like RabbitMQ and Kafka come in.

They act as intermediaries that:

📬 Guarantee message delivery, even if a service is down
⚡ Improve system performance via async processing
🔗 Allow cross-language communication between services

There are two main patterns:

Point-to-Point Messaging → Each message is delivered to exactly one consumer (e.g., financial transactions).
Publish/Subscribe Messaging → One message can be consumed by multiple subscribers (e.g., event notifications).

For example, in RabbitMQ:

Publisher sends messages to a queue/topic.
Consumer retrieves and processes them — even if it was offline when the message was sent.

Why Not Just Use REST APIs?

While REST APIs work, they lack fault tolerance. If a service is down when you send a request, the message is simply lost unless you add complex retry logic.

Message brokers handle this for you — buffering messages until the consumer is ready.

💡 In the full guide, I cover:

Deep dive into RabbitMQ & Kafka concepts
Point-to-Point vs Publish/Subscribe explained
Running RabbitMQ with Docker
Building .NET Publisher & Consumer apps step-by-step
Code samples you can run today

👉 Read the full tutorial here:

Message Brokers for Microservices: RabbitMQ, Kafka & Real Examples

💬 Do you use RabbitMQ, Kafka, or another message broker in your projects? Share your experience in the comments!