gecko-dev/services/settings/static-dumps
Mark Banner d1e65e8eb3 Bug 1875960 - Use the build system rather than package-manifest.in, to govern which remote settings dumps are packaged. r=leplatrem,firefox-build-system-reviewers,geckoview-reviewers,glandium,m_kato
Differential Revision: https://phabricator.services.mozilla.com/D206495
2024-04-09 08:18:20 +00:00
..
main
moz.build
readme.md

readme.md

Remote Settings Initial Data

In order to reduce the amount of data to be downloaded on first synchronization, a JSON dump from the records present on the remote server can be shipped with the release.

The dumps in this directory will NOT automaticaly be kept in sync with remote. This is useful for collections that benefit from a default iniital state but require dynamism beyond that - e.g. DoH regional configurations. For dumps that should automatially be kept in sync with remote, use ../dumps/.

Dumps from dumps/ and static-dumps/ are packaged into the same resource path, thus looking the same to the client code and also implying that filenames must be unique between the two directories.