OSTREE REMOTE(1) | ostree remote | OSTREE REMOTE(1) |
ostree-remote - Control remote repository configuration
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} {VALUE}
ostree remote list-cookies {NAME}
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.
--set="KEY=VALUE"
--if-not-exists
--force
--no-gpg-verify
--gpg-import=FILE
Equivalent to ostree remote gpg-import --keyring=FILE.
--collection-id=COLLECTION-ID
-u, --show-urls
-k, --keyring=FILE
This option may be repeated to import from multiple files, but may not be used in combination with --stdin.
--stdin
This option may not be used in combination with --keyring.
--raw
$ ostree remote show-url local
http://192.168.122.1/repo
OSTree |