MUNIN-GET(1)

💖 MUNIN-GET — the manual page, but make it slay 💖

okay bestie, sit down, hydrate, because we're about to talk about munin-get, and she's a section 1 girlie from the User Contributed Perl Documentation. That's right — user-contributed, which means she's the community's little princess. 👑

---

✨ NAME ✨

munin-get — a simple tool for managing plugins from remote repositories. That's it. That's the vibe. 🎀

---

🌸 FEATURES 🌸

The small management tool munin-get supports the following actions — and honestly? she does a lot for a "small" tool, we love a humble icon:

• clone one or more git repositories containing munin plugins 🧬
• multiple remote repositories can be used (yes bestie, you can stack them, we're poly-repo over here)
• list all found plugins, including change timestamp and description 📋
• "install" a plugin (by default to: /var/lib/munin-node/munin-get-plugins) 📦
• "enable" a plugin (create a symlink to /etc/munin/plugins/) 🔗
• upgrade plugins (and review changes before — look before you leap, angel) 🔍

The primary purpose of this tool is the simplification of the process of using plugins from munin's contrib repository. No cap, that's literally the whole point. 🫶

---

🌈 USAGE 🌈

All actions except install, enable and disable can be run as a regular user. Periodt. But listen — please note that the non-privileged commands use directories relative to $HOME by default (and yes, that can be overridden, go off). Thus sudo or a similar tool should be used for gaining privileges. And of course, everything can also be done as root — if that's your main character era, live your truth. 💅

The separate install step works around potential problems with systemd hardening flags or other security policies, which may prevent files in /root/ or below /home/ from being accessed by the munin-node service process. So like... it's not extra for no reason, she's being responsible. 🧚

---

🦋 EXAMPLES 🦋

💜 Discover, inspect, install, enable and test a plugin

munin-get update
munin-get list
munin-get search throughput
munin-get doc contrib/traffic
munin-get install contrib/traffic
munin-get enable contrib/traffic
munin-run traffic
service munin-node restart   # for systemd: systemctl restart munin-node

look at her go. discovery → inspection → install → enable → test. a full glow-up arc. ✨

💜 Review and apply changes from the upstream repository

munin-get update
munin-get list-upgradeable
munin-get diff-upgradeable
munin-get upgrade

peep the diff before you commit, bestie. that's the responsible queen behaviour. 👑

💜 Add custom 3rd party git repositories

munin-get add-repository foo http://example.org/repos/munin-plugins.git
munin-get add-repository bar http://example.org/repos/munin-stuff.git branch-tested plugins/
munin-get update

yesss add your little third-party repos, the more the merrier, we're building an empire here. 🔥

---

🌟 INTERNALS 🌟

Repositories are cloned below ~/.cache/munin/munin-get/repositories (see REPOSITORY_CACHE_BASE_DIR). Cozy little cache corner. 🏠

Manual changes in the cloned repositories should be avoided. Like, fr fr. Don't touch. Hands off. She's not yours. 😭

The separate install and enable procedure is necessary due to possible process namespace / hardening features enabled for munin-node. Thus the target of the symlink is located in a path that can be expected to be usable even for a restricted munin-node process. It's giving ✨thoughtful design✨.

Additionally the separate install location allows the manual review of upstream changes before applying these locally. Which, again — look before you leap. 🐇

---

🎀 AUTHOR 🎀

Lars Kruse <devel@sumpfralle.de> — the icon, the legend, the moment. 💖

---

📜 LICENSE 📜

GPLv3+

---

and that's the whole page, bestie!!! this was MUNIN-GET(1), part of the User Contributed Perl Documentation, brought to you by perl v5.42.3 and dated 2026-09-30. go forth, manage those plugins, and remember: review before you upgrade, always. 💖✨🎀🦋🌸