gecko-dev/services/settings/dumps
ffxbld 6a258cbbf9 No Bug, mozilla-central repo-update HSTS HPKP remote-settings tld-suffixes - a=repo-update r=RyanVM
Differential Revision: https://phabricator.services.mozilla.com/D116890
2021-06-04 20:23:51 +00:00
..
blocklists No Bug, mozilla-central repo-update HSTS HPKP remote-settings tld-suffixes - a=repo-update r=RyanVM 2021-06-04 20:23:51 +00:00
main Bug 1713606 - Add a new home for "static" Remote Settings dumps that don't need to be kept in sync with remote. r=leplatrem 2021-06-03 15:27:08 +00:00
pinning Bug 1694217 - manually run all remote-settings dumps through jq. r=RyanVM 2021-03-01 16:15:30 +00:00
security-state No Bug, mozilla-central repo-update HSTS HPKP remote-settings tld-suffixes - a=repo-update r=RyanVM 2021-06-04 20:23:51 +00:00
moz.build Bug 1654103: Standardize on Black for Python code in `mozilla-central`. 2020-10-26 18:34:53 +00:00
readme.md Bug 1713606 - Add a new home for "static" Remote Settings dumps that don't need to be kept in sync with remote. r=leplatrem 2021-06-03 15:27:08 +00:00

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.

A bot will update the files automatically. For collections that should not be kept in sync, put the JSON dumps in ../static-dumps/ instead.

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.