pbx-registry(1)

🦋 NAME 🦋

okay so pbx-registry is here to examine user registry, see and modify keys — that’s the whole serve, bestie. This is the pbx-registry(1) page from the General Commands Manual, section 1, main character energy 💅.

✨ SYNOPSIS ✨

pbx-registry [options] user [key [value]]

No cap, that’s the shape: options first, then a user, then optionally a key, and optionally a value 🫶.

💅 DESCRIPTION 💅

Sends a status request to a locally running coventry server to verify if a given user is valid. The exit code can then be used to branch shell scripts. iykyk — that’s the automation slay.

Optionally, you can request the value of a given user’s registry key item, or set the value of a feature key. Finally, the -c option can be used to clear all persistent settings for the given user.

🌸 OPTIONS 🌸

• --clear — clear a given user’s feature settings.
• --exists — tests if line is defined in config.
• --invite — tests if line can be invited.
• --message — tests if line can be messaged.
• --quiet — only return exit code, produce no output.
• --help — outputs help screen for the user.

🔥 EXIT STATUS 🔥

Exit status can be used to determine command results in shell scripts. This is the part your script is gonna vibe-check.

• 0 — Command sent and successfully processed.
• 1 — Command send resulted in an error or is invalid.
• 2 — Command timed out without any response signaled.
• 3 — Error sending to message queue.
• 4 — Message queue or shm ipc not found or inaccessible.

👑 COPYRIGHT 👑

Copyright © 2022 Tycho Softworks.

This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Cute sign-off: Tycho Softworks · Coventry — that’s the footer source/version vibe; the original footer doesn’t print a date, so no fake date, just vibes 🎀💖.