Build Production-Ready Apache Configurations

Apache Configuration Builder creates Apache HTTP Server configurations for web deployments, including virtual hosts, modules, security controls, TLS, performance tuning, URL rewriting, and monitoring. It covers Apache 2.4 and later, httpd.conf, mod_rewrite, and SSL/TLS configuration. Its baseline includes server identification, listen directives, explicit module loading, directory and location rules, and logging.

Security guidance includes disabling unnecessary modules, limiting server version details, applying access controls and security headers, setting modern TLS options, protecting sensitive files and .git directories, and configuring rate limiting when mod_evasive is available. Performance Examples include compression, browser caching, ETags, and rewriting URLs. Monitoring examples configure custom logs and restrict access to server status and information endpoints.

Use this agent when building or reviewing Apache configurations for a website or application, especially when HTTPS virtual hosts, security hardening, routing, caching, or observability are needed. It can generate configuration patterns and tune worker settings based on available memory and the chosen MPM.

Treat examples as starting points that must match the host, certificate paths, enabled modules, application routes, and network policy. The source explicitly recommends testing in development before production and maintaining separate configuration sets for dev, staging, and production. Keep backups and use version control. Review access restrictions carefully before exposing status or information endpoints.

Useful inputs include Apache version, operating system paths, hostnames, document roots, certificate locations, application routing needs, enabled modules, available memory, and monitoring requirements. Outputs may include a base server configuration, HTTP to HTTPS redirect, TLS virtual host, security directives, cache and compression rules, rewrite patterns, logging, and protected monitoring locations.

Use using separate files such as ssl.conf and security.conf, documenting custom directives, rotating logs, and updating Apache and modules. It also recommends checking configuration syntax before reload and maintaining backups of known working configurations. The selected MPM can be prefork, worker, or event; worker limits should be sized based on available memory.

The examples reference Apache modules such as mod_rewrite, mod_deflate, mod_expires, and mod_evasive, as well as fail2ban and Web Application Firewall rules. They cover TLS certificates, HSTS and other response headers, PHP pretty URLs, API routing, and the server status handler. These features require appropriate modules and local configuration.

This agent is for web administrators, DevOps engineers, and backend developers who maintain Apache HTTP Server. It is useful when a deployment needs a configuration that balances security, performance, routing, and operational visibility, with changes reviewed and tested before production.

apache2ctl configtest