What is Apache?
Apache HTTP Server (commonly apache2) is one of the longest-running and most
widely used web servers. It serves web content over HTTP/HTTPS and is known for
its flexible module system and support for per-directory configuration through
.htaccess files.
Apache is a good fit when an application expects Apache-specific behavior - for
example rewrite rules in .htaccess, or modules that only exist in the Apache
ecosystem. For many modern workloads, Nginx is faster and lighter, but Apache
remains the right choice when compatibility matters.
On TurboStack
Apache is the alternative web server on TurboStack. Nginx is the default and is recommended for most workloads, but you can switch a host to Apache when an app needs it.
-
Each host runs one web server. When Apache is selected, TurboStack provisions and manages
apache2for every application on that host. -
Apache is most useful when an application relies on
.htaccessfiles or Apache-specific modules that have no Nginx equivalent. -
As with Nginx, you select the web server at the host level rather than editing raw server config by hand.
Note
Apache and Nginx are mutually exclusive on a host - you choose one web server per host. If your app does not need Apache features, stay on Nginx.
Best practices
-
Choose Apache only when your application genuinely needs
.htaccessor an Apache-only module; otherwise prefer Nginx. -
Where possible, move rewrite and access rules out of
.htaccessand into application config for clarity and performance. -
Keep one web server per host and decide early - switching changes how every application on the host is served.
-
Always terminate Transport Layer Security (TLS) at the web server for every public application.