Maintainers:Fastly: Difference between revisions

imported>Thoughtpolice
No edit summary
update option names, fix syntax
Tags: Mobile edit Mobile web edit Visual edit
 
(3 intermediate revisions by one other user not shown)
Line 7: Line 7:
== Configuration details ==
== Configuration details ==


The core configuration details for our services are located in [https://github.com/nixos/fastly-config fastly-config] ('''TODO: LINK FIXME'''), which you can quickly clone with git:
The core configuration details for our services are located in [https://github.com/nixos/infra infra], which you can quickly clone with git:


{{Commands|$ git clone https://github.com/nixos/fastly-configs}}
{{Commands|$ git clone https://github.com/nixos/infra}}


Check the <code>README.md</code> for details about the structure of the project, how to make and contribute changes, etc. It also describes the rough architecture of the integration(s).
Check the <code>README.md</code> for details about the structure of the project, how to make and contribute changes, etc. It also describes the rough architecture of the integration(s).
Line 35: Line 35:
[https://github.com/thoughtpolice Austin] currently has a Fastly service configured implementing some of the above. To use it, you can change your <code>substituters</code> setting. '''This uses the real upstream S3 bucket''', so you do not need to trust any new signatures. For NixOS users:
[https://github.com/thoughtpolice Austin] currently has a Fastly service configured implementing some of the above. To use it, you can change your <code>substituters</code> setting. '''This uses the real upstream S3 bucket''', so you do not need to trust any new signatures. For NixOS users:


{{file|/etc/nixos/configuration.nix|nix|<nowiki>
{{file|||<nowiki>
{...}
{
{
   nix.binaryCaches = [ "https://aseipp-nix-cache.global.ssl.fastly.net" ]
   nix.settings.substituters = [ "https://aseipp-nix-cache.global.ssl.fastly.net" ];
}
}
</nowiki>}}
</nowiki>|name=/etc/nixos/configuration.nix|lang=nix}}


Nix users:
Nix users:
Line 52: Line 51:
==== Changelog ====
==== Changelog ====


We'll also have a changelog recording any major upgrades made to the service. You can view the current one here: https://aseipp-nix-cache.global.ssl.fastly.net/changelog
We'll also have a changelog recording any major upgrades made to the service. You can view the current one here: https://aseipp.notion.site/07c3be3df9f24d829471c6f8208a8570?v=41a80a849bb646d6a184bd1ce770edc4


==== Beta + IPv6 + HTTP/2 ====
==== Beta + IPv6 + HTTP/2 ====
Line 83: Line 82:
=== IPv6 shenanigans ===
=== IPv6 shenanigans ===


See [https://github.com/NixOS/nixpkgs/issues/65015]. Some users report that turning off IPv6 helps download things from <code>cache.nixos.org</code>. See also on the Fastly support forums: [https://support.fastly.com/hc/en-us/community/posts/360040169531-I-often-can-t-access-Fastly-servers-using-HTTPS-IPv6-RST-packets-received I (often) can't access Fastly servers using HTTPS+IPv6: RST packets received]. It is unclear how widespread this issue might be. Using an IPv4 only DNS CNAME may mitigate this in the long run.
See [https://github.com/NixOS/nixpkgs/issues/65015]. Some users report that turning off IPv6 helps download things from <code>cache.nixos.org</code>. See also on the Fastly support forums: [https://web.archive.org/web/20221208122000/https://support.fastly.com/hc/en-us/community/posts/360040169531-I-often-can-t-access-Fastly-servers-using-HTTPS-IPv6-RST-packets-received I (often) can't access Fastly servers using HTTPS+IPv6: RST packets received]. It is unclear how widespread this issue might be. Using an IPv4 only DNS CNAME may mitigate this in the long run.


== Future plans ==
== Future plans ==