| OSTREE REMOTE(1) | ostree remote | OSTREE REMOTE(1) |
.SH "NAME" ostree-remote - Control remote repository
configuration
.SH "SYNOPSIS"
.HP 432u
ostree remote add [OPTIONS...] {NAME} {URL} [BRANCH...]
.HP 504u
ostree remote delete {NAME}
.HP 552u
ostree remote show-url {NAME}
.HP 456u
ostree remote list [OPTIONS...] {NAME}
.HP 600u
ostree remote gpg-import [OPTIONS...] {NAME} [KEY-ID...]
.HP 672u
ostree remote gpg-list-keys {NAME}
.HP 456u
ostree remote refs {NAME}
.HP 528u
ostree remote summary [OPTIONS...] {NAME}
.HP 600u
ostree remote add-cookie
{NAME}
{DOMAIN}
{PATH}
{COOKIE_NAME}
{VALUE}
.HP 672u
ostree remote delete-cookie
{NAME}
{DOMAIN}
{PATH}
{COOKIE_NAME}
.HP 648u
ostree remote list-cookies {NAME}
.SH "DESCRIPTION"
.PP Changes remote repository configurations. The NAME refers to the name of
the remote.
.PP The BRANCH arguments to the add subcommand specifies the
configured branches for the remote. See the branches section in
ostree.repo-config(5) for more information.
.PP The gpg-import subcommand can associate GPG keys to a specific
remote repository for use when pulling signed commits from that repository
(if GPG verification is enabled). The gpg-list-keys subcommand can be
used to see the GPG keys currently associated with a remote repository.
.PP The GPG keys to import may be in binary OpenPGP format or ASCII armored.
The optional [KEY-ID] list can restrict which keys are imported from a
keyring file or input stream. All keys are imported if this list is omitted.
If neither --keyring nor --stdin options are given, then keys
are imported from the user's personal GPG keyring.
.PP The various cookie related command allow management of a remote specific
cookie jar.
.SH "ADD OPTIONS"
.PP --set="KEY=VALUE"
Set config option KEY=VALUE for remote.
.RE
.PP --if-not-exists
Do nothing if the provided remote exists.
.RE
.PP --force
Replace the provided remote if it exists.
.RE
.PP --no-gpg-verify
Disable GPG verification.
.RE
.PP --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). It does not disable GPG verification, which is enabled by default.
.RE
.PP --no-sign-verify
Disable signature verification. This disables GPG verification as well.
.RE
.PP --gpg-import=FILE
Import one or more GPG keys from a file.
Equivalent to ostree remote gpg-import --keyring=FILE.
.RE
.PP --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.
.RE
.SH "LIST OPTIONS"
.PP -u, --show-urls
Show remote URLs in list
.RE
.SH "REFS OPTIONS"
.PP --revision, -r
Also print the revisions for each ref. The revisions will be separated by a
tab character.
.RE
.PP --cache-dir=DIR
Use an alternate cache directory in DIR.
.RE
.SH "GPG-IMPORT OPTIONS"
.PP -k, --keyring=FILE
Import one or more keys from a file.
This option may be repeated to import from multiple files, but may not be used in combination with --stdin.
.RE
.PP --stdin
Import one or more keys from standard input.
This option may not be used in combination with --keyring.
.RE
.SH "SUMMARY OPTIONS"
.PP --cache-dir=DIR
Use an alternate cache directory in DIR.
.RE
.PP --raw
Show raw variant data
.RE
.SH "EXAMPLE"
.PP $ ostree remote show-url local
http://192.168.122.1/repo
| OSTree |