-
-
Notifications
You must be signed in to change notification settings - Fork 116
Cache NAR files for upto a year #727
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
NAR files are immutable. There is no harm in caching them for longer than the default 24 hours. It might save us on bandwidth cost to S3 and lower costs?
Does this only apply for successful (HTTP 200) responses? |
Because the We could perhaps add an explicit
to be 100% sure? |
What I'm worried about is that someone could abuse the negative cache and block new build results, so limiting the duration on 404 responses sounds good to me. |
So I think this is already the behaviour due to this rule https://github.com/NixOS/infra/blob/main/terraform/cache.tf#L233-L240 But we can add the explicit |
This allows us to test them in staging environment (I think?)
Okay this should now deploy the changes to staging environment as opposed to applying immediately. Would love to apply this pairing together with someone |
NAR files are immutable. There is no harm in caching them for longer than the default 24 hours. It might save us on bandwidth cost to S3 and lower costs?