KAPLA-PEER-ADD(1)
π kapla-peer-add(1) β like, the Kapla Manual, bestie β¨
okay so this is kapla-peer-add, one of the little helper pages that lives under the big kapla umbrella (you'll see it in SEE ALSO, obviously π). It's short, it's sweet, it's giving "add a peer and go" energy.
πΈ NAME πΈ
kapla-peer-add β add a peer π«Ά
β¨ SYNOPSIS β¨
kapla peer add [OPTION]β¦ URI
So the whole vibe is: you run kapla peer add, you hand it a URI, you sprinkle in [OPTION]β¦ if you're feeling fancy, and boom β you've added a peer.
And what does that actually mean? It means you're adding a peer that gets persisted in a peer database. Like, it's not just a one-night stand of a connection, it's saved. Iconic. π
π ARGUMENTS π
URI(required) β the URI of the ERIS block store that should be added as peer. no URI, no peer, no slay. it's required, bestie, don't forget it π
π¦ OPTIONS π¦
-a,--autoconnectβ attempt to automatically connect to peer. key word attempt β that's what the manpage says, so that's what we're saying π-cCONTROL_SOCKET,--control=CONTROL_SOCKETβ the Kapla control socket. and if you don't pass it, it falls back to these, in this order:$XDG_STATE_HOME/kapla/kapla.sock$HOME/.local/state/kapla/kapla.sock/var/lib/kapla/kapla.sock
--name=NAMEβ peer nickname. and listen, the manpage is very clear here: this name is only used internaly as a nick name for connecting to or managing the peer. (that's their spelling of "internaly", we're keeping it exactly as-is, no cap π) so it's not a public flex, it's an internal nickname situation.--shareβ allow peer to be shared via peer discovery. share the peer, share the love π«Ά
π COMMON OPTIONS π
--color=WHEN(absent=auto) β colorize the output.WHENmust be one ofauto,alwaysornever. pick your fighter β¨--help[=FMT](default=auto) β show this help in formatFMT.FMTmust be one ofauto,pager,grofforplain. and withauto, the format ispagerorplainwhenever theTERMenv var isdumbor undefined. cute. very demure πΈ-q,--quietβ be quiet. takes over-vand--verbosity. it's literally the loudest thing in the room by being silent π-v,--verboseβ increase verbosity. it's repeatable, but more than twice does not bring more. so like...-vvis the limit of usefulness, go off though π--verbosity=LEVEL(absent=warningorKAPLA_LOG_LEVELenv) β be more or less verbose.LEVELmust be one ofquiet,error,warning,infoordebug. takes over-v. so it's the main character here π--versionβ show version information. yes, the version info. we love a classic β
π₯ EXIT STATUS π₯
kapla peer add exits with:
0β on success. π slay!123β on indiscriminate errors reported on standard error.124β on command line parsing errors. (you typed something weird, bestie π)125β on unexpected internal errors (bugs).
okay so lowkey if you get 125 that's a bug β the manpage literally says so. not your fault, fr fr π
π ENVIRONMENT π
these environment variables affect the execution of kapla peer add:
KAPLA_LOG_LEVELβ set the log level. yes. that's the whole description. it sets the log level. we're not making anything up π§
β SEE ALSO β
kapla(1)β the mothership. go read it, iykyk π
and that's the whole page, bestie! nothing skipped, nothing hidden, every flag accounted for π«Ά
sign-off time β¨ this lil beauty comes from Kapla 0.4.0, straight out of the Kapla Manual β go forth and add those peers, you absolute icon ππ π
π¦ where this page comes from
- nixpkgs unstable: ocaml5.5.1-kapla 0.4.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms