ostree-remote - Control remote repository configuration
Contents
'Add' Options
--set="KEY=VALUE"
Set config option KEY=VALUE for remote.
--if-not-exists
Do nothing if the provided remote exists.
--force
Replace the provided remote if it exists.
--no-gpg-verify
Disable GPG verification.
--gpg-import=FILE
Import one or more GPG keys from a file.
Equivalent to ostreeremotegpg-import--keyring=FILE.
--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.
'Gpg-Import' Options
-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.
--stdin
Import one or more keys from standard input.
This option may not be used in combination with --keyring.
'List' Options
-u,--show-urls
Show remote URLs in list
'Refs' Options
--revision, -r
Also print the revisions for each ref. The revisions will be separated by a tab character.
--cache-dir=DIR
Use an alternate cache directory in DIR.
'Summary' Options
--cache-dir=DIR
Use an alternate cache directory in DIR.
--raw
Show raw variant data
Description
Changes remote repository configurations. The NAME refers to the name of the remote.
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.
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.
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.
The various cookie related command allow management of a remote specific cookie jar.
Example
$ostreeremoteshow-urllocalhttp://192.168.122.1/repo OSTree OSTREEREMOTE(1)
Name
ostree-remote - Control remote repository configuration
Synopsis
ostreeremoteadd [OPTIONS...] {NAME} {URL} [BRANCH...]
ostreeremotedelete {NAME}
ostreeremoteshow-url {NAME}
ostreeremotelist [OPTIONS...] {NAME}
ostreeremotegpg-import [OPTIONS...] {NAME} [KEY-ID...]
ostreeremotegpg-list-keys {NAME}
ostreeremoterefs {NAME}
ostreeremotesummary [OPTIONS...] {NAME}
ostreeremoteadd-cookie {NAME} {DOMAIN} {PATH} {COOKIE_NAME} {VALUE}
ostreeremotedelete-cookie {NAME} {DOMAIN} {PATH} {COOKIE_NAME} {VALUE}
ostreeremotelist-cookies {NAME}
