Puppetboard

Puppetboard is a visual dashboard for monitoring your puppet infrastructure.

  • Infrastructure
  • Monitoring & Logging
Puppetboard is a visual dashboard for monitoring your puppet infrastructure. It transforms complex data into clear charts and lists, allowing you to see which servers are running correctly, identify errors quickly, and track changes across your entire network through a simple web interface.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

60/100 Good

Maintained
100last commit 1 day ago
Popular
57735 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
No data
Security check
201 serious finding, 1 minor, CI, tests, OpenSSF Scorecard 7.1/10

Based on 4 of 5 factors.

GitHub stars
735
Open issues
75
Last commit
2026-11-20
Latest release
v8.1.0
License
Apache-2.0
Activity
declining

Checked yesterday - source: GitHub (voxpupuli/puppetboard)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Set PuppetDB address, port, and secret In the Docker command, set PUPPETDB_HOST and PUPPETDB_PORT to your PuppetDB server (the place that stores Puppet data) before starting. Also replace SECRET_KEY with a long random string; without the correct address it has no data to show, and without a strong secret the web session is not properly protected. source
  • Use --net=host or publish a port The quickstart uses --net=host, which means the container shares your computer's network instead of needing a separate published port. If you remove that flag but do not publish a port, the app may start but your browser will not be able to reach it. source
  • Mount PuppetDB HTTPS keys if needed If your PuppetDB uses HTTPS, create /etc/puppetboard on your machine with its key.pem and cert.pem, mount that folder into the container, and set PUPPETDB_KEY and PUPPETDB_CERT. Missing or unreadable certificates can stop Puppetboard from connecting securely to PuppetDB. source

Fetched 48 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Why is Puppetboard unreachable in Docker after I stop using --net=host?

If you remove --net=host, you need to publish a port so the browser can reach the container. Without a published port, the app may start but remain unreachable.

What Docker environment settings are required to point Puppetboard at PuppetDB?

Set PUPPETDB_HOST and PUPPETDB_PORT to your PuppetDB server and replace SECRET_KEY with a long random string. Without a strong secret, the web session is not properly protected.

How should Puppetboard be configured for an HTTPS PuppetDB?

Mount a folder containing PuppetDB's key.pem and cert.pem into the container and set PUPPETDB_KEY and PUPPETDB_CERT. Missing or unreadable certificates can stop Puppetboard from connecting securely.

How can I serve Puppetboard through Apache?

The Puppet module includes puppetboard::apache::vhost, which uses the official Puppet Labs Apache module's apache::vhost defined type to create a full virtual host.

Answers sourced from context7.com, forge.puppet.com

Community

Collected 48 days ago - public community threads