| 1 Jun 2025 |
 edef | we can fetch into s3 on the aws side, pulling from fastly | 11:50:12 |
| edef | whether that is wise is another question, but we can definitely do it | 11:50:27 |
| edef | mostly it is isomorphic to having hydra have a more-local / free-egress storage service | 11:51:49 |
| edef | and using s3 mostly as archival storage | 11:52:05 |
 toonn | That's certainly better than Hydra pushing to S3 and Fastly pulling from it preferentially but won't most of the Fastly cache still be clobbered by the S3 requests? So in the end Fastly would fetch many things from Hydra twice still? | 12:29:43 |
 flokli | We can also do the push through thing. So instead of hydra uploading to fastly or s3 directly, it'd send to a http daemon that uploads to both places | 13:47:44 |
| flokli | It gives nicer control over the import path | 13:48:01 |
| edef | yes, these are all essentially identical in terms of dataflow | 13:48:06 |
