npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

haconfig

v0.0.1

Published

Combines multiple files to build a HAProxy config

Downloads

3

Readme

HAconfig

Small script to build a haproxy.cfg file from multiple files. Useful if you want to drop some service specific configs into a directory then re-render haproxy.cfg and reload.

Warning: I hacked this together in a short space of time with minimal thought/testing - I wouldn't recommend using it anywhere that matters.

Usage

haconfig /path/to/template/directory > /etc/haproxy/haproxy.cfg

Templates files

The HAProxy config is built using multiple files in a single directory - they can be called whatever you like and will be loaded in alphabetical order.

templates/
    bar.cfg
    base.cfg
    foo.cfg

/etc/haproxy/templates/base.cfg

The files can look like a regular haproxy.cfg.

global
    log 127.0.0.1	local0
    log 127.0.0.1	local1 notice
    maxconn 4096
    user haproxy
    group haproxy

defaults
    log	global
    mode	http
    option	httplog
    option	dontlognull
    retries	3
    option redispatch
    maxconn	2000
    timeout connect 5000
    timeout client 50000
    timeout server 50000

frontend http_in
    bind *:80
    acl is_foo hdr_beg(host) -i foo
    use_backend foo if is_foo

backend foo
    server foo1 127.0.0.1:8080 check
    server foo2 127.0.0.1:8081 check

/etc/haproxy/templates/global2.cfg

If you define the same section in multiple files you'll get an error:

# THIS DOESN'T WORK - clashes with base.cfg!

global
    foo bar
    testing 123

/etc/haproxy/templates/bar.cfg

However, you can extend sections using the extend keyword:

extend frontend http_in
    acl is_bar hdr_beg(host) -i bar
    use_backend bar if is_bar

backend bar
    server bar1 127.0.0.1:8082
    server bar2 127.0.0.1:8083

/etc/haproxy/haproxy.cfg

Combining the above templates/base.cfg and templates/bar.cfg files will produce the following output:

global
    log 127.0.0.1	local0
    log 127.0.0.1	local1 notice
    maxconn 4096
    user haproxy
    group haproxy

defaults
    log	global
    mode	http
    option	httplog
    option	dontlognull
    retries	3
    option redispatch
    maxconn	2000
    timeout connect 5000
    timeout client 50000
    timeout server 50000

frontend http_in
    bind *:80
    acl is_bar hdr_beg(host) -i bar
    use_backend bar if is_bar
    acl is_foo hdr_beg(host) -i foo
    use_backend foo if is_foo

backend bar
    server bar1 127.0.0.1:8082
    server bar2 127.0.0.1:8083

backend foo
    server foo1 127.0.0.1:8080 check
    server foo2 127.0.0.1:8081 check