About Linux Dork
Why this Linux blog exists and what you can expect from it.
What Is Linux Dork
Linux Dork is a nerdy command-line journal for people who have already made the choice. It started as a place to document configurations that took too long to figure out and grew into a full reference for practical Linux workflows, self-hosted infrastructure, and the tooling that actually earns its place on a server.
The focus is on things that run in a terminal, survive a reboot, and don't require a GUI to manage. That means shell patterns you can copy directly, Docker Compose stacks you can actually maintain, and write-ups on self-hosted apps that have been stress-tested beyond the initial setup screen.
If you're here, the preamble is unnecessary; this is just the notes.
What Gets Covered
- Shell & CLI
Bash patterns, zsh plugins, terminal multiplexers, and the aliases you wish you'd set up years ago.
- Desktop Linux
Window managers, theming, HiDPI, font rendering: the perpetual fine-tuning of a daily driver.
- Self-Hosting
600+ self-hosted apps catalogued. Docker Compose stacks, reverse proxies, backup strategies, and what actually survives contact with real use.
- Security & SSH
Hardening servers, key management, firewall rules, and sensible defaults for anything exposed to the internet.
- Automation
Cron, systemd timers, Ansible, and the point where shell scripts become maintenance problems.
- Linux News
Kernel releases, distro updates, and security advisories, filtered for the stuff that actually matters.
Editorial Rules
Reversible by default
If a change can't be undone cleanly, the post will say so clearly, and usually suggest a backup step first.
Runnable snippets
Code blocks are tested. If something is from memory or approximate, that gets called out explicitly.
No filler
Posts skip the "What is Linux?" preamble. If you're here you've already booted into a terminal at least once.
Opinionated but justified
Preferences get stated plainly, with the reasoning attached. You can disagree, and often you'd be right.
The full process, from sourcing and testing to updates and corrections, is in our editorial standards. Guides are written by the Linux Dork editorial team.
Recent Posts
- AMD GPUs on Linux: amdgpu, Mesa, Vulkan, and ROCm Explained
- Core Dumps on Linux: Debugging Crashes With coredumpctl
- CrowdSec vs Fail2ban: Blocking Attackers on Linux Servers
- Debugging Bash Scripts: set -x, PS4, and ShellCheck