flatpak-remote-add (1) - Linux Man Pages
flatpak-remote-add: Add a remote repository
flatpak-remote-add - Add a remote repository
- flatpak remote-add [OPTION...] NAME LOCATION
Unless overridden with the --user or --installation options, this command changes the default system-wide installation.
The following options are understood:
- Show help options and exit.
- Assume the URI is a .flatpakrepo file rather than the repository itself. This is enabled by default if the extension is .flatpakrepo, so generally you don't need this option.
- Modify the per-user configuration.
- Modify the default system-wide configuration.
- Modify a system-wide installation specified by NAME among those defined in /etc/flatpak/installations.d/. Using --installation=default is equivalent to using --system.
- Disable GPG verification for the added remote.
- Set the priority for the remote. Default is 1, higher is more prioritized. This is mainly used for graphical installation tools.
- Mark the remote as not enumerated. This means the remote will not be used to list applications, for instance in graphical installation tools.
- Mark the remote as not to be used for automatic runtime dependency resolution.
- Do nothing if the provided remote already exists.
- Disable the added remote.
- A title for the remote, e.g. for display in a UI.
- A single-line comment for the remote, e.g. for display in a UI.
- A full-paragraph description for the remote, e.g. for display in a UI.
- URL for a website for the remote, e.g. for display in a UI.
- URL for an icon for the remote, e.g. for display in a UI.
- A default branch for the remote, mainly for use in a UI.
Add a local filter to the remote. A filter file is a list of lines, each file starting with "allow" or "deny", and then a glob for the ref to allow or disallow. The globs specify a partial ref (i.e. you can leave out trailing parts which will then match everything), but otherwise only "*" is special, matching anything in that part of the ref.
By default all refs are allowed, but if a ref matches a deny rule it is disallowed unless it specifically matches an allow rule. This means you can use this to implement both whitelisting and blacklisting.
Here is an example filter file:
# This is a whitelist style filter as it denies all first deny * allow runtime/org.freedesktop.* allow org.some.app/arm allow org.signal.Signal/*/stable allow org.signal.Signal.*/*/stable
- Import gpg keys from the specified keyring file as trusted for the new remote. If the file is - the keyring is read from standard input.
- Specify the authenticator to use for the remote.
- Specify an authenticator option for the remote.
- Enable auto-installation of authenticator.
- Disable auto-installation of authenticator.
- Print debug information during command processing.
- Print OSTree debug information during command processing.
$ flatpak remote-add gnome https://sdk.gnome.org/gnome.flatpakrepo
$ flatpak --user remote-add --no-gpg-verify test-repo https://people.gnome.org/~alexl/gnome-sdk/repo/
flatpak(1), flatpak-remote-modify(1), flatpak-remote-delete(1), flatpak-remotes(1), flatpak-flatpakrepo(5)