What will change?
- Website is now built by Github Actions which will push the result to Netlify.
- You can see the preview of the website: https://nixos-homepage.netlify.com
- All static release artifacts (e.g. tarballs) have been moved to https://releases.nixos.org. (Nixpkgs and NixOS artifacts were already hosted there.)
- Channels (
/channels/<project>-<version|channel>), which are basically redirects to https://releases.nixos.org, are being migrated to https://channels.nixos.org, which is just another S3 bucket which handles redirects for us.
- More about all of the setup you can find at the following links
How will this affect me?
As we separate the website from its infrastructure, there is going to be a small yet important change that everybody will have to make.
To install latest Nix you are most likely using the command advertise on the website:
curl https://nixos.org/nix/install | sh
curl https://nixos.org/releases/nix/nix-<version>/install | sh
This will need to be changed to:
curl -L https://nixos.org/nix/install | sh
curl -L https://nixos.org/releases/nix/nix-<version>/install | sh
When will this change happen?
Ideally we would like to deploy this yesterday. We actually already tried switching to netlify only to find out that this is breaking all installations of Nix. For now migration plan is the following:
- On Saturday (2020-03-14 at 11:00 CET) we will switch serving the website from Netlify, but install script (https://nixos.org.nix/install) will be included in the website therefore (1) installing of Nix works as before (2) we can continue working on nixos.org
- Next month (on 2020-04-15) we will bring the install script redirect back. That would require everybody to use the
-Loption when installing Nix via curl. In the meantime we will also make sure that Travis / Github Actions integrations are updated. This should give you enough time to adjust your build systems accordingly.
Make sure you mark those dates in your calendar or better fix your scripts now !
Why are you switching to Netlify?
We are switching away from the current server because we would like to reduce the maintenance burden. At the same time this change will empower anybody that wishes to do changes to the website without risk, since it won’t mess up NixOS channels. And Netlify was chosen because it is a well-known service, which offers very good integration with Github (previews in Pull Requests among other things).
You missed something…
Please let us know if you are using any part of the infrastructure that is being moved and we will gladly make the needed adjustments on time.
I wish your builds to always be green.