git-annex-registerurl(1)

πŸ’– git-annex-registerurl(1) β€” General Commands Manual πŸ’–

okay so bestie, welcome to the git-annex-registerurl page, straight out of the General Commands Manual ✨ this one's a lil niche but it's lowkey iconic once you get it, trust.

🌸 NAME 🌸

git-annex-registerurl β€” it registers an url for a key, that's the whole vibe πŸŽ€

πŸ¦‹ SYNOPSIS πŸ¦‹

git annex registerurl [key url]

✨ DESCRIPTION ✨

So this is a plumbing-level command, meaning it's the gears-and-sprockets layer, not the cute porcelain stuff you'd hand to your non-Unix friends. What it does: you can use it to register urls where a key can be downloaded from πŸ’…

⚠️ Heads up bestie: no verification is performed of the url's contents. Like, zero. None. It does not check anything. It just believes you. πŸ™ˆ

Normally the key is a git-annex formatted key. But β€” and this is the slay part β€” to make it easier to use this to add urls, if the key cannot be parsed as a key, and is a valid url, a VURL key is constructed from the url. So it kinda meets you where you're at 🫢

Registering an url also makes git-annex treat the key as present in the special remote that claims it. (Usually the web special remote.) main character energy for the web remote, honestly πŸ‘‘


πŸ’œ OPTIONS πŸ’œ

  • --remote=name|uuid β€” says hey, this url is expected to be claimed by the specified remote. And if some other remote claims the url instead? Registering it will fail. no cap, it will simply not go through 😭
Little note: --remote=web will prevent any other remote from claiming the url. web remote said "mine" and meant it πŸ’€
  • --batch β€” batch input mode! Lines are read from stdin, and each line should contain a key and url, separated by a single space. πŸ“

For backwards compatability with old git-annex before this option was added, when no key and url pair are specified on the command line, batch input is used, the same as if the --batch option were specified. It is however recommended to use --batch. (Yes, the old behaviour is still lurking. It's giving legacy. But bestie, just say --batch out loud, it's clearer ✨)

  • -z β€” when in batch mode, the input is delimited by nulls instead of the usual newlines. weird lil divider but ok, we respect it πŸŽ€

(Note that for this to be used, you have to explicitly enable batch mode with --batch. Like, -z alone is not gonna manifest batch mode out of thin air, bestie 🧚)

  • --json β€” enable JSON output. This is intended to be parsed by programs that use git-annex. Each line of output is a JSON object. machine-readable slay πŸ€–πŸ’–
  • --json-error-messages β€” messages that would normally be output to standard error are included in the JSON instead. so the errors get to live inside the JSON, cozy 🌈

Also the git-annex-common-options(1) can be used. free real estate, go off πŸ‘‘


πŸ”₯ SEE ALSO πŸ”₯

the whole url-lore cinematic universe, honestly, go read them all 🌸


🌟 AUTHOR 🌟

Joey Hess <id@joeyh.name> β€” iconic, we stan πŸ’œ


and that's the page, bestie πŸŽ€ this is git-annex-registerurl(1) from the git-annex manual β€” go forth and register those urls, you absolute legend πŸ¦‹πŸ’…

πŸ“¦ where this page comes from