RPYC_CLASSIC(1)

💖 NAME 💖

rpyc_registry — bestie, it's the RPyC registry 👑

✨ SYNOPSIS ✨

rpyc_registry [options]

🦋 DESCRIPTION 🦋

okay so first things first: RPyC (say it with me — "are-pie-see" 🌈) aka Remote Python Call is a transparent Python library for symmetrical remote procedure calls, clustering and distributed-computing. literally what. it uses something called object-proxying, which is this technique that leverages Python's dynamic nature to overcome the physical boundaries between processes and computers, so that remote objects can be manipulated as if they were local. no cap, that's the whole magic trick ✨

rpyc_registry is the lil matchmaker that provides a way for clients to discover running instances of rpyc_classic(1) servers 🫶 so like, your clients can find your servers. iconic behaviour honestly.

The following options are available:

• --mode MODE, -m MODE — pick your registry service type, bestie. It can be TCP or UDP (and UDP is the default, fyi 💅).
• --port PORT, -p PORT — choose the UDP/TCP listener port for the registry. The default is 18811 ⭐
• --timeout SECS, -t SECS — set a timeout after which unresponsive servers will be removed from the registry. The default is 240 seconds ⏳
• --logfile FILE — write log to FILE. If not specified, log output is written to stderr 📝
• --quiet, -q — quiet mode. Only errors will be logged 🤫

👀 SEE ALSO 👀

rpyc_classic(1) — go read that one too, fr fr 🎀

🌸 AUTHOR 🌸

This manual page was written for Debian by Timo Röhling and may be used without restriction 💜

and that's the whole vibe check, bestie — this page is from the Remote Python Call (RPyC) crew, filed under RPYC_CLASSIC(1), and it's giving manual page, periodt 🎀✨💅