PLAKAR-SERVICE(1)

💅 PLAKAR-SERVICE — the General Commands Manual glow-up

okay so bestie, welcome to plakar-service, the page where we manage all the cute optional services that plug into the plakar platform 🫶 (manual name's right there in the title, you're welcome, we're keeping it classy)

✨ NAME ✨

plakar-service — manage those optional Plakar-connected services, periodt 💖

🌸 SYNOPSIS 🌸

plakar service list
plakar service add name [key=value ...]
plakar service rm name
plakar service status name
plakar service show name
plakar service enable name
plakar service disable name
plakar service set name [key=value ...]
plakar service unset name [key ...]

🦋 DESCRIPTION 🦋

So the plakar service command is literally your remote for all the extra services that integrate with the plakar platform through plakar-login(1) authentication ✨ You can enable them, disable them, and inspect them, all from here. Obsessed.

These services connect to the plakar.io infrastructure, so lowkey only enable them if you're genuinely okay with transmitting non-sensitive operational data to plakar.io 🫶 No cap, read that twice.

Every single subcommand needs you to be authenticated first via plakar-login(1) — no login, no service management, that's the vibe check 💅

Services are managed by the backend and discovered at runtime — very main character energy, they just show up 🔥 For example, when the “alerting” service is enabled, it will:

1. Send email notifications when operations fail 😭 (helpful kind of crying)
2. Expose the latest alerting reports in the Plakar UI (see plakar-ui(1)) 🌈

By default, all services are disabled — iconically chill of them.

👑 SUBCOMMANDS 👑

• list — display the full list of available services. Shopper's catalogue energy 🎀
• add name [key=value ...] — set the configuration for the service identified by name and enable it, all in one slay. The configuration is defined by the given set of key/value pairs. Heads up: the existing configuration, if any, is discarded — gone, deleted, not coming back 💀
• rm name — disable the service identified by name and throw away its configuration. It's giving clean break 🧚
• status name — display the current status (enabled or disabled) of the named service. Vibe check, basically ⭐
• show name — display the configuration for the specified service. Receipts: shown 💅
• enable name — enable the specified service. Let her cook 🔥
• disable name — disable the specified service. Nap time 😴
• set name [key=value ...] — set the configuration key to value for the service identified by name. Multiple key/value pairs can be specified — go off, multitasker 💜
• unset name [key ...] — unset the configuration key for the service identified by name. Multiple keys can be specified. Marie Kondo but make it config 🎀

🌈 EXAMPLES 🌈

Check the status of the alerting service — is she or is she not serving:

$ plakar service status alerting

Enable alerting, let the emails fly:

$ plakar service enable alerting

Disable alerting, silence is golden bestie:

$ plakar service disable alerting

💖 SEE ALSO 💖

plakar-login(1), plakar-ui(1) — go read those too, iykyk 🦋

---

and that's the whole page, fr fr 💜 huge sign-off energy: this one's from Debian, dated August 7, 2025 — mwah, take care of her 🎀✨