haproxy

HAProxy load balancer and proxy. Use for high-availability.

7 stars

byG1Joshi

View on GitHub Installation ↓

Best use case

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

HAProxy load balancer and proxy. Use for high-availability.

Teams using haproxy 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/haproxy/SKILL.md --create-dirs "https://raw.githubusercontent.com/G1Joshi/Agent-Skills/main/skills/devops/haproxy/SKILL.md"

Manual Installation

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

How haproxy Compares

Feature / Agent	haproxy	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?

HAProxy load balancer and proxy. Use for high-availability.

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

# HAProxy

HAProxy is the standard for high-performance load balancing. HAProxy 3.0 (2025) adds **Syslog Load Balancing** and improved HTTP/3 QUIC support.

## When to Use

- **High Traffic**: Handling millions of requests per second.
- **L4 Balancing**: TCP proxying for Database replicas, Redis, or non-HTTP protocols.
- **Advanced Logic**: Complex ACLs, rate limiting, and sticky sessions.

## Quick Start

```haproxy
frontend http_front
   bind *:80
   default_backend web_servers

backend web_servers
   balance roundrobin
   server web1 10.0.0.1:80 check
   server web2 10.0.0.2:80 check
```

## Core Concepts

### Frontend / Backend

Frontend defines how requests enter (ports, certs). Backend defines where they go and how (algorithms, health checks).

### ACLs

Access Control Lists. Powerful conditionals.
`acl is_api path_beg /api`
`use_backend api_servers if is_api`

### Stick Tables

In-memory storage for tracking events (e.g. rate limiting by IP).

## Best Practices (2025)

**Do**:

- **Use Data Plane API**: For dynamic configuration without reloads.
- **Enable Prometheus Exporter**: Built-in metrics endpoint.
- **Tune `maxconn`**: Critical for preventing resource exhaustion.

**Don't**:

- **Don't use as Web Server**: It is a proxy. Use Nginx/Caddy for serving static files.

## References

- [HAProxy Documentation](https://www.haproxy.org/)