That sounds great! Thanks for the work. I’ve a few comments below.
- 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.
I only get an Error: [object Object] when I load
https://channels.nixos.org that page. Curl only reports a bunch of JS on
the site. Is that intended?
On the current version I can use lynx (or any other text browser on the
installer) to navigate the channel list.
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).
I think this is the right move. We have to empower more people to
contribute to everything relating to the project.
Did you follow up with them on the IPv6 topic? In 2020 that should be
part of technical baseline requirements. I accept that in the past this
wasn’t possible due to some AWS/NixOps/… issue(s).
It is already bad enought that we require IPv4 due to strictly only
using GitHub.com for contributions. Seeing the website being deployed to
a v4 only service at this day makes my networking heart cry.
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.
What will happen to https://nixos.org/~eelco ? I usually use that to
link to the Nix related papers (e.g.
https://nixos.org/~eelco/pubs/phd-thesis.pdf) that Eelco authored. The
preview (https://nixos-homepage.netlify.com) doesn’t seem to support
that. Would be a shame to see the relevant docs be only visible on
3rd-party websites.