JetBrains plugin

HAProxy Language Support for JetBrains IDEs

Catch HAProxy config mistakes while editing in a JetBrains IDE, with the same language server and rules as HAProxy Config for VS Code.

Open source and maintained by Juan Torchia.

How to check an HAProxy config before reload →

Current release
v0.2.0
Marketplace downloads
146
Observed Nov 12, 2026
Compatibility
JetBrains 2026.1.4+ / platform build 261.26222+; HAProxy 2.4–3.4
License
MIT

A focused tool for a specific workflow

Version-aware HAProxy configuration validation, completion, hover documentation, and backend navigation in IntelliJ IDEA, PyCharm, and other JetBrains IDEs.

  • Version-aware diagnostics for HAProxy 2.4 through 3.4: unknown directives, wrong sections, out-of-range ports, unitless timeouts, deprecated options, and undefined backends
  • Syntax highlighting, completion for directives and option variants filtered by section, and hover documentation with the version that introduced each directive
  • Go to definition and rename for backends

From install to a safer decision

  1. Install HAProxy Language Support from JetBrains Marketplace in an IDE based on 2026.1 or later, and make Node.js available on PATH.
  2. Choose the HAProxy version in Settings | Languages & Frameworks | HAProxy, and set the Node.js executable there if it is not on PATH.
  3. Open an HAProxy .cfg or .conf file and use the inline diagnostics, completion, hover documentation, and backend navigation while editing.
  4. Run HAProxy's own configuration check and deployment validation before applying the change.

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 plugin registers HAProxy files with the IntelliJ Platform LSP support and a TextMate grammar for syntax highlighting.

  2. It bundles the HAProxy Config 0.6.1 language server from the released VS Code extension on Open VSX; the build pins its version and SHA-256 checksum and fails if the download differs.

  3. Node.js runs the server, which applies the HAProxy version chosen in the settings to produce diagnostics, completion, hover documentation, definitions, and renames, so rules match the VS Code extension.

Inspect the implementation on GitHub

Supported scope

  • haproxy.cfg, haproxy.conf, haproxy*.cfg, and .cfg or .conf files inside a haproxy/ directory
  • Other .cfg and .conf files that start HAProxy sections and are not claimed by another plugin
  • Per-IDE HAProxy version selection

Explicit boundaries

  • Diagnostics are editor feedback, not a substitute for running the matching HAProxy binary with its configuration check before reload or deployment.
  • Node.js is required for validation, completion, hover, and navigation; without it only syntax highlighting works and the IDE shows a warning.
  • When filing public issues, use a minimal sanitized configuration and remove hosts, addresses, credentials, certificates, and other production details.
Read the security policy

Get help, verify changes, or contribute

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

Need this kind of workflow inside your team?

Start with a bounded workflow review. Product support stays in public issues; organization-specific discovery and implementation follow a private path.

Review the engagement