table of contents
- testing 1.2.4-1
- stretch-backports 1.2.4-1~bpo9+1
- unstable 1.2.4-1
- experimental 1.4.2-1
FLATPAK REMOTE(5) | flatpak remote | FLATPAK REMOTE(5) |
NAME¶
flatpak-remote - Configuration for a remoteDESCRIPTION¶
Flatpak stores information about configured remotes for an installation location in $installation/repo/config. For example, the remotes for the default system-wide installation are in $prefix/var/lib/flatpak/repo/config, and the remotes for the per-user installation are in $HOME/.local/share/flatpak/repo/config.Normally, it is not necessary to edit remote config files directly, the flatpak remote-modify command should be used to change properties of remotes.
System-wide remotes can be statically preconfigured by dropping config fragments into /etc/flatpak/remotes.d/.
FILE FORMAT¶
The remote config file format is using the same .ini file format that is used for systemd unit files or application .desktop files.[remote ...]¶
All the configuration for the the remote with name NAME is contained in the [remote "NAME"] group.The following keys are recognized by OSTree, among others:
url (string)
gpg-verify (boolean)
gpg-verify-summary (boolean)
This is ignored if collection-id is set, as refs are verified in commit metadata in that case. Enabling gpg-verify-summary would break peer to peer distribution of refs.
collection-id (string)
All flatpak-specific keys have a xa. prefix:
xa.disable (boolean)
xa.prio (integer)
xa.noenumerate (boolean)
xa.nodeps (boolean)
xa.title (string)
xa.title-is-set (boolean)
xa.default-branch (string)
xa.default-branch-is-set (boolean)
xa.main-ref (string)
EXAMPLES¶
[remote "gnome-nightly-apps"] gpg-verify=true gpg-verify-summary=true url=https://sdk.gnome.org/nightly/repo-apps/ xa.title=GNOME Applications
[remote "flathub"] gpg-verify=true gpg-verify-summary=false collection-id=org.flathub.Stable url=https://dl.flathub.org/repo/ xa.title=Flathub
SEE ALSO¶
flatpak-remote-modify(1)flatpak |