Help › If our servers are down
Keep your own copy
On this page
Four ways to keep a copy, from least to most work.
1. WordPress does it for you#
The plugin copies your published files to wp-content/uploads/resilientlang/ and serves them first from your own domain. Back that folder up with the rest of your site.
2. Download the published files#
The command-line tool can download and verify the published bundle without a secret key:
rl pull --base <origin> --public-key <key> --site-key <key>
You get a folder with the manifest and one file per language. Put it on your own web server, in the layout v1/<site key>/.... The loader can then use your server as one of its places, through the data-base setting. See The command-line tool.
3. Build translated pages into your site#
The framework kits write translated pages into your own build output. After that, your site serves them without any call to us. See Install on a static site.
4. Export the translations#
An export gives you the text itself in standard formats. It is the ownership guarantee, and it is independent from the published files. See Export your translations.
The loader file#
With the script tag the loader comes from our CDN. To remove that dependency, use a numbered loader address, download that file, and serve it from your own site. Check the setup with your own tests: verify.
How often#
Download or export after each publish that matters, and store it with your other backups. Published files are small.