VS Code extension

HAProxy Config for VS Code

Catch section, directive, reference, deprecation, and version mistakes while editing—not during a production reload.

Open source and maintained by Juan Torchia.

How to check an HAProxy config before reload →

Install from marketplaceView source
Current release
v0.6.0
Compatibility
VS Code 1.110+; HAProxy 2.4–3.4
License
MIT
VS Code Marketplace
248 installs
Observed 2026-09-29; totals change over time.
What it does

A focused tool for a specific workflow

Version-aware HAProxy configuration validation, completion, hover documentation, formatting, and navigation inside VS Code.

  • Version-aware diagnostics for HAProxy 2.4 through 3.4, including deprecated and unavailable directives
  • Context-aware completion, hover documentation, snippets, quick fixes, formatting, folding, and symbols
  • Definition, reference, highlight, and rename support for configuration relationships
Workflow

From install to a safer decision

  1. Install the extension and open an HAProxy .cfg or .conf file.
  2. Select the HAProxy version used by that workspace from the status bar or command palette.
  3. Review inline diagnostics and use completion, hover help, navigation, formatting, and quick fixes while editing.
  4. Run HAProxy's own configuration check and deployment validation before applying the change.
Architecture

How the pieces fit together

This is a textual architecture map grounded in the public implementation. Follow the source link to inspect the exact modules, tests, and release history.

  1. The VS Code client activates for HAProxy configuration files and owns editor commands and workspace settings.

  2. The client exchanges Language Server Protocol messages with a bundled TypeScript language server; Node.js does not need to be installed separately on the target machine.

  3. The server parses the document and consults versioned directive metadata before producing diagnostics, completion, hover, formatting, symbols, definitions, references, highlights, renames, and code actions.

Inspect the implementation on GitHub
Inputs

Supported scope

  • HAProxy .cfg and .conf files
  • Per-workspace HAProxy version selection
Privacy and security

Explicit boundaries

  • Diagnostics are editor feedback, not a substitute for running the matching HAProxy binary with its configuration check before reload or deployment.
  • When filing public issues, use a minimal sanitized configuration and remove hosts, addresses, credentials, certificates, and other production details.
Read the security policy
Public project

Get help, verify changes, or contribute

Issues and release history stay with the source repository so the evidence remains public.

Get support or report an issueRead release notes