GNUNET-DID(1)

✨ GNUNET-DID(1) ✨

okay bestie, welcome to gnunet-did(1) — yes it's a manual page, yes it's a whole vibe, and yes it lives in the General Commands Manual section of your friendly neighbourhood man setup. sit down, hydrate, let's go 💅

🌸 NAME 🌸

gnunet-did — a command line tool to create and manage gnunet identity DIDs. literally the whole personality. no cap.

🎀 SYNOPSIS 🎀

gnunet-did [-A | --show-all] [-C | --create]
           [-c FILENAME | --config=FILENAME] [-d DID | --did=DID]
           [-D DID_DOCUMENT | --did-document=DID_DOCUMENT]
           [-e EGO | --ego=EGO] [-g | --get] [-h | --help]
           [-L LOGLEVEL | --loglevel=LOGLEVEL]
           [-l LOGFILE | --logfile=LOGFILE] [-r | --remove]
           [-R | --replace] [-s | --show]
           [-t TIME | --expiration-time=TIME] [-v | --version]

look at her. all those little flags holding hands. 🫶

🦋 DESCRIPTION 🦋

so gnunet-did is a command line tool to create and manage gnunet identity DIDs. that's the tea. that's the mission statement. she creates, she manages, she does not elaborate further because the OPTIONS section is right there and she's about to spill everything 👑

💖 OPTIONS 💖

one bullet per flag, exactly as promised, no skipping, no shortcuts (iykyk):

• -A | --show-all — list all the DIDs for all the egos. everyone's invited to this party, it's giving open guest list 🌈
• -C | --create — create a DID Document and display the DID. glow-up moment, the DID is born and immediately shown off 📸
• -c FILENAME | --config=FILENAME — use the specified configuration file FILENAME. point her at your config, she'll read it, no questions asked 🎀
• -d DID | --did=DID — the DID to use for the operation is DID. yes bestie, this is the DID we're talking about. this one right here ✨
• -D DID_DOCUMENT | --did-document=DID_DOCUMENT — the DID Document to use is DID_DOCUMENT. she's carrying a whole document around, main character energy fr fr 📄
• -e EGO | --ego=EGO — the ego to use is EGO. the ego in question. that one. we love her 💜
• -g | --get — get the DID Document associated with the DID given in DID. retrieval era, we're fetching 💫
• -h | --help — print short help on options. when in doubt, ask for help. iconic behaviour, always valid 🫶
• -L LOGLEVEL | --loglevel=LOGLEVEL — use LOGLEVEL for logging. valid values are DEBUG, INFO, WARNING and ERROR. pick your chaos level wisely 👀
• -l LOGFILE | --logfile=LOGFILE — configure logging to write logs to LOGFILE. receipts go in the file, not the group chat 🗂️
• -r | --remove — remove the DID given in --did. we're doing a little cleanup, a little decluttering, very satisfying 🧹
• -R | --replace — replace the DID Document given in --did-document for the DID given in DID. out with the old doc, in with the new 💅
• -s | --show — show the DID for the ego given in --ego. a little reveal, a little spotlight moment 🔥
• -t | --expiration-time — the expiration time to use in the GNS record for the DID Document given in DID_DOCUMENT. yes, everything has a shelf life, even DIDs. set your TIME and let her live her life ⏳
• -v | --version — print GNUnet version number. the classic. the "which build am I on" check. no notes ⭐

📚 SEE ALSO 📚

the full documentation for gnunet is maintained as a Texinfo manual. if the info(1) and gnunet programs are properly installed at your site, the command

info gnunet

should give you access to the complete handbook. go read it, it's the extended lore, the director's cut 🍓

💀 BUGS 💀

found a bug? report bugs by using https://bugs.gnunet.org or by sending electronic mail to ⟨gnunet-developers@gnu.org⟩. they genuinely want to hear from you, it's not a trap, go tell them 🙈

and that's the whole page bestie, you ate that 💖

signing off from the Debian build of this page, dated January 5, 2023, in the GNUNET-DID(1) section of the General Commands Manual — periodt. 👑✨