Tracking issue: Refactor site deployment

Marigold commented 1 month ago

Our deployment process is unnecessarily complex right now. We haven't changed it when migrating from Netlify to Cloudflare and there easy ways how to simplify it:

[ ] Our site is built into ~/live-data/bakedSite, it could be just ~/bakedSite
[ ] Deploy scripts are in owid-grapher repo, but it'd be more natural to have them in ops (since they are similar to staging servers)
[ ] Is the 20000 file limit by Cloudflare still relevant (as a workaround we serve those files from R2)? There's grapher/exports that contains ~9000 files which can make it impossible

danyx23 commented 1 month ago

In #3746 Ike tried to get rid of one of the main uses of static chart thumbnails (the other being chart admin preview images). We are a lot closer to being able to delete the static charts now but it would mean reviving that PR and bringing it over the finishing line.

danyx23 commented 1 month ago

The first two points I think you can just do, @Marigold, there is no good reason not to. The third point needs a bit of work on the Grapher side.

Marigold commented 1 month ago

Thanks for the heads-up. It's by no means important, serving files from R2 has been working surprisingly well.

owid / owid-grapher

Tracking issue: Refactor site deployment #3985