OSTREE-REMOTE(1)

πŸ’… OSTREE-REMOTE β€” the ostree remote girlies' manual πŸ’…

okay so bestie, you're reading the ostree remote page β€” that's the ostree remote manual, section 1. This is where you control remote repository configuration. Let's get into it, no cap. ✨


πŸŽ€ NAME πŸŽ€

ostree-remote β€” control remote repository configuration. that's it, that's the vibe. πŸ’–


πŸ¦‹ SYNOPSIS πŸ¦‹

like, here's every single way you can call her:

ostree remote add [OPTIONS...] {NAME} {URL} [BRANCH...]

ostree remote delete {NAME}

ostree remote show-url {NAME}

ostree remote list [OPTIONS...] {NAME}

ostree remote gpg-import [OPTIONS...] {NAME} [KEY-ID...]

ostree remote gpg-list-keys {NAME}

ostree remote refs {NAME}

ostree remote summary [OPTIONS...] {NAME}

ostree remote add-cookie {NAME} {DOMAIN} {PATH} {COOKIE_NAME} {VALUE}

ostree remote delete-cookie {NAME} {DOMAIN} {PATH} {COOKIE_NAME}

ostree remote list-cookies {NAME}

🌸 DESCRIPTION 🌸

So this whole command changes remote repository configurations. easy. And NAME? that's literally just the name of the remote. main character identifier energy. πŸ‘‘

The BRANCH arguments on the add subcommand specify the configured branches for the remote. if you wanna know more about that, go read the branches section in ostree.repo-config(5). iykyk. πŸ“š

The gpg-import subcommand can associate GPG keys to a specific remote repository β€” which gets used when pulling signed commits from that repository (but only if GPG verification is enabled, bestie, don't forget that part). And gpg-list-keys is the one that lets you peek at which GPG keys are currently associated with a remote repository. πŸ‘€

The GPG keys you import can be in binary OpenPGP format or ASCII armored. fancy. The optional [KEY-ID] list can restrict which keys get imported from a keyring file or input stream β€” if you omit that list, all the keys get imported. And hear me out: if you give neither --keyring nor --stdin, then keys are imported from the user's personal GPG keyring. πŸ—οΈ

The various cookie-related commands let you manage a cookie jar that's specific to one remote. πŸͺ literally jars of cookies, obsessed.


✨ ADD OPTIONS ✨

  • --set="KEY=VALUE" β€” set config option KEY=VALUE for the remote. πŸ› οΈ
  • --if-not-exists β€” do nothing if the provided remote already exists. chill mode, no drama. 😌
  • --force β€” replace the provided remote if it exists. she does not ask twice. πŸ’…
  • --no-gpg-verify β€” disable GPG verification. 🚫
  • --sign-verify=KEYTYPE=[inline|file]:PUBKEY β€” require commits to be signed by the given public key. KEYTYPE names a signature engine β€” currently ed25519. The key is given either literally, as inline:PUBKEY, or as a path to a file of keys, as file:/path/to/keys.

This writes the sign-verify option and the matching verification-KEYTYPE-key or verification-KEYTYPE-file companion β€” see ostree.repo-config(5). Important tho: it does not disable GPG verification, which is enabled by default. so don't come for me. πŸ™ˆ

  • --no-sign-verify β€” disable signature verification. and yes, this disables GPG verification as well. both. gone. πŸ’€
  • --gpg-import=FILE β€” import one or more GPG keys from a file.

It's equivalent to ostree remote gpg-import --keyring=FILE. same thing, cuter outfit. πŸŽ€

  • --collection-id=COLLECTION-ID β€” set the collection ID for the remote to a value provided by the repository owner, which allows refs from this remote to be shared peer to peer. cute AND collaborative. 🫢

⭐ LIST OPTIONS ⭐

  • -u, --show-urls β€” show remote URLs in list. πŸ”—

🌈 REFS OPTIONS 🌈

  • --revision, -r β€” also print the revisions for each ref. the revisions get separated by a tab character. yes, a literal tab. ⭐
  • --cache-dir=DIR β€” use an alternate cache directory in DIR. πŸ—‚οΈ

🧚 GPG-IMPORT OPTIONS 🧚

  • -k, --keyring=FILE β€” import one or more keys from a file.

You can repeat this option to import from multiple files β€” but you may not use it in combination with --stdin. pick a lane bestie. 🚫

  • --stdin β€” import one or more keys from standard input.

This option may not be used in combination with --keyring. same rule, other direction. πŸ’€


πŸ”₯ SUMMARY OPTIONS πŸ”₯

  • --cache-dir=DIR β€” use an alternate cache directory in DIR. πŸ—‚οΈ
  • --raw β€” show raw variant data. unfiltered, unedited, raw. πŸ’€

πŸ“ EXAMPLE πŸ“

like, here's the moment:

$ ostree remote show-url local
            http://192.168.122.1/repo

slay. that's the URL, right there. πŸ”₯


ok that's the whole page bestie, go configure some remotes and be iconic about it πŸ’œ

signing off πŸ’– β€” this has been the OSTree edition of the ostree remote manual page, section 1, OSTREE REMOTE(1). mwah. πŸŽ€βœ¨

πŸ“¦ where this page comes from