FLATPAKREPO(5)

NAME
flatpakrepo - Reference to a remote

DESCRIPTION

Flatpak uses flatpakrepo files to share information about remotes. The flatpakrepo file contains enough information to add the remote. Use the flatpak remote-add --from command to do so.

flatpakrepo files may also contain additional information that is useful when displaying a remote to the user, e.g. in an app store.

The filename extension commonly used for flatpakrepo files is .flatpakrepo.

flatpakrepo files can also be placed in /usr/share/flatpak/remotes.d/ and /etc/flatpak/remotes.d/ to statically preconfigure system-wide remotes. Such files must use the .flatpakrepo extension. If a file with the same name exists in both, the file under /etc will take precedence.

FILE FORMAT

The flatpakrepo file is using the same .ini file format that is used for systemd unit files or application .desktop files.

  [Flatpak Repo]

All the information is contained in the [Flatpak Repo] group.

The following keys can be present in this group:

Version (uint64)
    The version of the file format, must be 1 if present.

Url (string)
    The url for the remote. This key is mandatory.

GPGKey (string)
    The base64-encoded gpg key for the remote.

DefaultBranch (string)
    The default branch to use for this remote.

Subset (string)
    Limit the remote to the named subset of refs.

Title (string)
    The title of the remote. This should be a user-friendly name that can be displayed e.g. in an app store.

Comment (string)
    A short summary of the remote, for display e.g. in an app store.

Description (string)
    A longer description of the remote, for display e.g. in an app store.

Icon (string)
    The url for an icon that can be used to represent the remote.

Homepage (string)
    The url of a webpage describing the remote.

Filter (string)
    The path of a local file to use to filter remote refs. See flatpak-remote-add(1) for details on the format of the file.

    Note: This field is treated a bit special by flatpak remote-add. If you install a remote with --if-not-exists then and the remote is already configured, then the filter field of the remote configuration will be update anyway. And, if the filter field is *not* specified then any existing filters are cleared. The goal here is to allow a pre-configured filtered remote to be replaced with the regular one if you add the normal upstream (unfiltered) flatpakrepo file.

DeploySideloadCollectionID (string)
    The collection ID of the remote, if it has one. This uniquely identifies the collection of apps in the remote, to allow peer to peer redistribution (see flatpak(1)). It is recommended to use this key over DeployCollectionID or CollectionID because only newer clients (Flatpak 1.12.8 or later) pay attention to it (and older clients don't handle collection IDs properly).

DeployCollectionID (string)
    This is deprecated but still supported for backwards compatibility. Use DeploySideloadCollectionID instead.

CollectionID (string)
    This is deprecated but still supported for backwards compatibility. Use DeploySideloadCollectionID instead.

EXAMPLE

    [Flatpak Repo]
    Title=gedit
    Url=http://sdk.gnome.org/repo-apps/

    DeployCollectionID=org.gnome.Apps

SEE ALSO

flatpak(1), flatpak-remote-add(1), flatpakref(5)