RPYC_CLASSIC(1)

πŸ’… RPYC_CLASSIC(1) β€” the rpyc_classic era πŸ’…

okay bestie, sit down, grab a boba, because we're about to talk about rpyc_classic, from the General Commands Manual section. it's giving ✨ infrastructure ✨ and honestly? we're obsessed.


🌸 NAME 🌸

rpyc_classic β€” the RPyC classic server. yes that's the whole name, she's simple, she's iconic πŸ’–


πŸ¦‹ SYNOPSIS πŸ¦‹

rpyc_classic [options]

that's it. that's the whole vibe. options go brrr πŸŽ€


✨ DESCRIPTION ✨

okay so. RPyC β€” pronounced "are-pie-see", which is honestly a serve β€” stands for Remote Python Call. it's a transparent Python library for symmetrical remote procedure calls, clustering and distributed-computing. no cap.

the way it works?? RPyC uses object-proxying, a 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. literally main character energy. the objects don't even know they're remote. periodt. πŸ’…

rpyc_classic is the server component which enables remote access to the local system. she's the one holding it down on the machine. the following options are available, and yes we're going through every single one, don't scroll 🫢

πŸŽ€ OPTIONS πŸŽ€

  • --mode MODE, -m MODE β€” pick your mode of operation, bestie. one of threaded, forking, stdio, oneshot. choose wisely, each one's got a different vibe πŸ”₯
  • --port PORT, -p PORT β€” the TCP port the server listens on. the default is 18812 for unauthenticated instances and 18821 for SSL authenticated ones. she adapts πŸ’…
  • --host INTERFACE β€” bind to the network interface INTERFACE. the default is localhost, so she's staying home unless you tell her otherwise 🏠
  • --ipv6 β€” enable IPv6. glow up for your network stack ⭐
  • --logfile FILE β€” write the log to FILE. if you don't specify one, log output goes to stderr. so it's still gonna be loud, don't worry πŸ™ˆ
  • --quiet, -q β€” quiet mode. only errors will be logged. she's in her calm era 🀫

🌈 RPyC Registry 🌈

a server instance can be registered with a running rpyc_registry(1) for automated service discovery by clients. so your clients can just find her. iconic.

  • --registry-type TYPE β€” connect to the registry via TCP or UDP (which is the default). UDP is the chill one πŸ’œ
  • --registry-port PORT β€” connect to the registry on port PORT. the default is 18811 ✨
  • --registry-host HOST β€” connect to the registry at host HOST. this is a required option for TCP registries, no skipping it bestie. if no host is specified for UDP, the server will attempt a broadcast via IP 255.255.255.255 to reach any listening registry in the local network. she's yelling into the void, and honestly? it works πŸ“’

πŸ”₯ SSL Authenticated Mode πŸ”₯

the server supports authentication and authorization via SSL certificates. very secure, very demure... except, no, actually:

WARNING: While this mode provides a modest amount of security, there are serious shortcomings such as a missing certificate revocation mechanism. Do not rely on this to expose vital infrastructure to the Internet. πŸ’€ bestie please. do not do that. i am begging.

you need to specify the following options to enable this mode:

  • --ssl-cafile FILE β€” read the Certificate Authority (CA) certificate from FILE. the CA is used to determine which client certificates are authorized to connect to the server; only client certificates which have been issued by the CA are accepted.
WARNING: If this option is omitted, the server will allow any client to connect, which is probably not what you want. 😭 not the open door policy. absolutely not.
  • --ssl-certfile FILE β€” read the SSL server certificate from FILE. this certificate is presented to connecting clients to let them verify that the server is genuine. she's showing her ID at the door πŸͺͺ
  • --ssl-keyfile FILE β€” read the private SSL server key for the server certificate from FILE. guard this with your life, fr fr πŸ”

πŸ‘€ SEE ALSO πŸ‘€

that's her sister. go say hi.


πŸ‘‘ AUTHOR πŸ‘‘

this manual page was written for Debian by Timo Râhling and may be used without restriction. slay, thank you Timo 🫢


and that's the whole page bestie!! from the General Commands Manual, it's rpyc_classic(1) β€” go forth, run your server, and remember: remote objects are just local objects with main character energy. bye ily πŸ’–βœ¨πŸ¦‹πŸŒΈπŸ’