apache

Apache HTTP Server web server. Use for traditional web hosting.

7 stars

byG1Joshi

View on GitHub Installation ↓

Best use case

apache is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Apache HTTP Server web server. Use for traditional web hosting.

Teams using apache should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/apache/SKILL.md --create-dirs "https://raw.githubusercontent.com/G1Joshi/Agent-Skills/main/skills/devops/apache/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/apache/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How apache Compares

Feature / Agent	apache	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

Apache HTTP Server web server. Use for traditional web hosting.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Apache HTTP Server (httpd)

Apache is a robust, modular web server. While Nginx leads in raw performance, Apache leads in **flexibility** via `.htaccess`. v2.4 remains the stable standard in 2025.

## When to Use

- **Shared Hosting**: `.htaccess` allows per-directory config without restarting the server.
- **Dynamic Modules**: Loading modules without recompiling.
- **Legacy Apps**: Many PHP/Perl apps are pre-tuned for Apache.

## Core Concepts

### MPM (Multi-Processing Modules)

- `prefork`: Compatible with non-thread-safe libraries (old PHP).
- `event`: Modern, async I/O. Best for high concurrency.

### VirtualHosts

Serving multiple domains from one IP.

### .htaccess

Files in the web root that override config. Convenient but slows performance.

## Best Practices (2025)

**Do**:

- **Use `event` MPM**: It rivals Nginx in connection handling.
- **Disable `.htaccess`**: If you have root access, put config in `httpd.conf` `Directory` blocks for performance.
- **Use HTTP/2**: Enable `mod_http2`.

**Don't**:

- **Don't enable unnecessary modules**: Reduce attack surface.

## References

- [Apache HTTP Server Documentation](https://httpd.apache.org/docs/2.4/)