Skip to main content
Expert

The web server that powered much of my early Drupal consulting work and remains a trusted foundation for many production websites.

Visit website

Why I use it

Apache has been part of my Drupal journey almost from the beginning, so I'm comfortable with both its strengths and its quirks. I appreciate its flexibility and the breadth of its ecosystem, particularly when supporting legacy applications or environments where stability and compatibility are more important than pursuing the latest technology.

How I use it

Apache HTTP Server has been one of the cornerstones of web development throughout my career. For many years it served as the standard web server for Drupal, providing the flexibility and reliability needed to host everything from small organizational websites to large enterprise platforms. Its extensive module ecosystem and mature configuration options made it well suited to the diverse requirements of Drupal projects.

I've deployed and maintained Apache across numerous Drupal environments, configuring virtual hosts, URL rewriting, SSL, caching behavior, and PHP integration. Whether working on local development environments, traditional LAMP stacks, or managed hosting platforms, Apache has consistently been a dependable part of my toolkit.

For clients, Apache represents a proven and well-understood platform backed by decades of development and community support. While newer alternatives have emerged, it remains an excellent choice for many organizations depending on their infrastructure and operational requirements.