I’m sure you’ve heard the famous developer phrase, “But it works on my machine!” It became a meme for a reason. Differences in environments, library versions, and system configurations often lead to chaos. Docker solves this problem by packaging an application and all its dependencies into isolated units called containers.

This article is your all-in-one Docker cheat sheet. I’ve gathered everything I find essential, from running your first container to advanced cleanup techniques and Dockerfile best practices.

I got tired of constantly editing my /etc/hosts file for every new project. I wanted to use clean, convenient local domains like project-one.app.loc or api.my-app.app.loc without having to define each one manually.

My solution is Dnsmasq, a lightweight DNS server that is perfect for this task. It allows me to set up wildcard domains (e.g., *.app.loc), where any subdomain automatically points to my local machine. It’s a set-it-and-forget-it setup that has saved me countless hours.

In this guide, I’ll walk you through how I set up dnsmasq on modern Linux distributions like Ubuntu 24.04 and Fedora 42. I’ll also show you how I resolve the common conflict with the default systemd-resolved service to create a powerful and convenient local development environment.

Welcome, and congratulations on installing Fedora! A fresh OS is a blank slate, and this is your chance to craft it into something perfect for you. This guide is a collection of my personal post-install steps, refined over time, designed to get a system perfectly tuned for development and everyday tasks.

Think of this as your personal checklist to quickly get everything in order—from essentials like NVIDIA drivers and Docker to the finer details like custom fonts, a powerful terminal, and handy GNOME extensions. Don’t treat this as a rigid script. Tailor it to your workflow: skip what you don’t need and add your own favorite tools. Ultimately, the goal is to create a setup that feels like home and makes your daily work a pleasure.