FLATPAK-REMOTE-ADD(1)
π FLATPAK-REMOTE-ADD π
okay bestie, so this is the flatpak-remote-add page from the flatpak manual (section 1), and it's genuinely one of the most useful little commands ever. let's get into it π«Ά
β¨ NAME β¨
flatpak-remote-add β Add a remote repository
πΈ SYNOPSIS πΈ
flatpak remote-add [OPTION...] NAME LOCATION
π¦ DESCRIPTION π¦
So basically, this command adds a remote repository to the flatpak repository configuration. periodt. β¨
NAME is the name you're giving the new remote, and LOCATION is a url or a pathname. Now here's the tea: LOCATION is either a flatpak repository itself, or a .flatpakrepo file that describes a repository. And in that first case (where it's the repo itself, not the cute descriptor file), you might also have to specify extra options β like the gpg key for the repo. iykyk. π
Unless you override it with the --user or --installation options, this command changes the default system-wide installation. no cap.
π OPTIONS π
The following options are understood:
-h,--helpβ Show help options and exit.--fromβ Assume the URI is a.flatpakrepofile rather than the repository itself. This is enabled by default if the extension is.flatpakrepo, so generally you don't need this option.-u,--userβ Modify the per-user configuration.--systemβ Modify the default system-wide configuration.--installation=NAMEβ Modify a system-wide installation specified byNAMEamong those defined in/etc/flatpak/installations.d/. Using--installation=defaultis equivalent to using--system.--no-gpg-verifyβ Disable GPG verification for the added remote.--prio=PRIOβ Set the priority for the remote. Default is1, higher is more prioritized. This is mainly used for graphical installation tools. It is also used when searching for a remote to provide an app's runtime. The app's origin is checked before other remotes with the same priority.--subset=SUBSETβ Limit the refs available from the remote to those that are part of the named subset.--no-enumerateβ Mark the remote as not enumerated. This means the remote will not be used to list applications, for instance in graphical installation tools.--no-use-for-depsβ Mark the remote as not to be used for automatic runtime dependency resolution.--if-not-existsβ Do nothing if the provided remote already exists.--disableβ Disable the added remote.--title=TITLEβ A title for the remote, e.g. for display in a UI.--comment=COMMENTβ A single-line comment for the remote, e.g. for display in a UI.--description=DESCRIPTIONβ A full-paragraph description for the remote, e.g. for display in a UI.--homepage=URLβ URL for a website for the remote, e.g. for display in a UI.--icon=URLβ URL for an icon for the remote, e.g. for display in a UI.--default-branch=BRANCHβ A default branch for the remote, mainly for use in a UI.--filter=PATHβ 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 allowlisting and blocklisting.
Here is an example filter file:
# This is an allowlist 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
--gpg-import=FILEβ 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.--signature-lookaside=URLβ Specify an URL to be used to look up signatures for this remote (OCI remotes only).--authenticator-name=NAMEβ Specify the authenticator to use for the remote.--authenticator-option=KEY=VALUEβ Specify an authenticator option for the remote.--authenticator-installβ Enable auto-installation of authenticator.--no-authenticator-installβ Disable auto-installation of authenticator.--no-follow-redirectβ Do not followxa.redirect-urldefined in the summary file.-v,--verboseβ Print debug information during command processing.--ostree-verboseβ Print OSTree debug information during command processing.
π EXAMPLES π
$ 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/
π SEE ALSO π
flatpak(1), flatpak-remote-modify(1), flatpak-remote-delete(1), flatpak-remotes(1), flatpakrepo(5)
and that's the whole page bestie!! π this one came from the flatpak source, FLATPAK REMOTE-ADD(1) β go add a remote, you're literally the main character of your own repo config πβ¨
π¦ where this page comes from
- fedora 44: flatpak 1.18.4-1.fc44 Β· LGPL-2.1-or-later
- fedora 44: flatpak 1.18.4-1.fc44 Β· LGPL-2.1-or-later
- nixpkgs unstable: flatpak 1.18.4
- ubuntu stonking: flatpak 1.18.4-1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms