My Experience Learning Omarchy & Arch Linux: A Productive Developer Setup (And Why I Use Docker for Legacy PHP)

I wouldn't call myself an Arch Linux guru or master. Rather, I am a backend developer who decided to dive into Arch Linux and Omarchy to see if it could genuinely improve my daily development speed. After months of daily use across client tasks and production codebases, the verdict is clear: it is remarkably productive.

Stripping away desktop bloat, eliminating window clutter, and configuring a keyboard-driven workflow transformed how I work. However, it wasn't without real learning curves — especially when dealing with older PHP versions on a bleeding-edge system. Here is an honest recap of my experience and what worked best.

1. Why Learning Omarchy & Arch Linux Was Worth It

Before switching, my development machine constantly felt bogged down by background processes, bloated desktop managers, and mouse gymnastics. Omarchy offered a focused, minimal alternative:

• Ultra-Light Resource Footprint: Idle system consumes ~350MB of RAM. The remaining 97%+ of my memory is completely available for heavy MySQL instances, Redis caches, and compilation tasks.
• Keyboard-First Speed: Tiling window managers make navigation instantaneous. You move between your code editor, database terminal, and browser without ever having to touch a mouse or hunt for windows.
• Native Command Execution: Shell commands, Git operations, and tests run natively on the Linux kernel with zero virtualization latency compared to WSL2 or macOS Docker abstractions.

"Once your system responds instantly to every keystroke without lag, it's very hard to go back to heavy, bloated desktop environments."

2. The Real-World Challenge: Older PHP Versions on Arch

Arch Linux is famous for being a rolling-release distribution. This means you always get the latest Linux kernel, the latest GCC, the newest OpenSSL 3+, and current ICU libraries.

For modern stacks like PHP 8.2+, Laravel 11, and Symfony 7, this is amazing — everything installs cleanly via pacman and executes at blistering speed.

However, in real-world backend jobs, you often have to support or maintain existing legacy codebases (such as projects on PHP 7.4 or CodeIgniter 3). That's where I ran into a real problem:

• Trying to download or compile older PHP packages from the AUR (Arch User Repository) frequently failed because older PHP builds rely on deprecated OpenSSL 1.1 APIs and older C libraries.
• Manually symlinking older libraries or patching makefiles risked corrupting system dependencies.
• Fighting package conflicts on the host OS was wasting time that should have been spent coding.

3. The Solution: Keep Arch Clean and Use Docker for Legacy PHP

After experimenting, the golden rule became clear: never pollute your Arch host system trying to force legacy versions to compile natively.

Instead, the most productive workflow is:

1. Host System: Keep Arch Linux lean, fast, and equipped with the latest native PHP 8+ and modern tools (Neovim, VS Code, Git, Starship).
2. Legacy Projects: Run them inside lightweight Docker containers using docker compose.

A simple docker-compose.yml handles legacy PHP (e.g. PHP 7.4-fpm + Nginx + MySQL) in complete isolation:

services:
  app:
    image: php:7.4-fpm-alpine
    volumes:
      - ./:/var/www/html
    restart: unless-stopped

  web:
    image: nginx:alpine
    ports:
      - "8080:80"
    volumes:
      - ./:/var/www/html
      - ./docker/nginx.conf:/etc/nginx/conf.d/default.conf
    depends_on:
      - app

With this separation, legacy projects spin up in seconds without breaking host libraries, and your Arch workstation stays pristine, stable, and blisteringly fast.

4. My Daily Productivity Setup

A few tools that tie the whole setup together:

• Terminal: Alacritty with JetBrains Mono Nerd Font.
• Shell & Navigation: Zsh + Starship prompt + zoxide for rapid directory jumping.
• Git Workflow: Custom aliases like git huddle to instantly review yesterday's commits.
• Containers: Docker daemon running locally with rootless permissions.

Conclusion

Adopting Omarchy and Arch Linux isn't about bragging rights — it's about building an environment that respects your time and lets you focus on code. If you're considering the switch, go for it! Just remember: use Docker for older runtime versions, and enjoy the speed.