Advanced hosting
To put a store online, most people need only Publish a permanent link: chronozarr publish uploads the store, checks it and prints the viewer link. The pages below are for setting up a host by hand, for hosts that publish does not cover, and for checking and tuning a host.
| I want to | Page |
|---|---|
| Set up Amazon S3 with CloudFront, Cloudflare R2, Google Cloud Storage or Source Cooperative by hand | Hosting recipes |
Upload a store without chronozarr publish | Upload without chronozarr publish |
Check a host, verify it by hand or fix a failing doctor check | Requirements and checks |
| Learn why every version needs a new prefix, and the upload order | Immutable prefixes and upload order |
| Add timesteps to a store that is already online | Append timesteps |
| Keep a store private | Private stores |
| Serve the viewer from my own host | Self-host the viewer |
What a host must do
A store is a folder of static files. Any host that serves files can serve it, with no server code, if it does these things:
- It returns each file at its path, and
404for a file that does not exist. - It sends
Access-Control-Allow-Origin: *, or the address of the viewer, so that the browser may read the files. - It returns the stored bytes unchanged. It does not compress them again.
- For a sharded store, it answers byte-range requests.
A store is unsharded unless you chose --shard, so most stores need only the first three. To check a host, run:
chronozarr doctor https://data.example.org/my_storedoctor checks each requirement and prints what to change. The requirements page lists every check. Measurements and dates are in the measurement log.