You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 29, 2024. It is now read-only.
Having the binary cache directly on an s3 domain name is a significant risk for not being able to fix a situation of excessive s3 transfer cost or migrate to different hosting.
It should be moved behind a CNAME alias on a domain you control for now so it could e.g. have a CDN in front like cache.nixos.org or allow migration to different hosting without changing external clients.
The text was updated successfully, but these errors were encountered:
As this is a prototype we may not rush to fix it until we decide to invest in the project for production, but I'll leave this open to keep track of the issue
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Bug report
Having the binary cache directly on an s3 domain name is a significant risk for not being able to fix a situation of excessive s3 transfer cost or migrate to different hosting.
It should be moved behind a CNAME alias on a domain you control for now so it could e.g. have a CDN in front like cache.nixos.org or allow migration to different hosting without changing external clients.
The text was updated successfully, but these errors were encountered: