Website migration

[rvagg]

• SSL certificates owned by the Node.js Foundation for *.nodejs.org and *.iojs.org
  • This is done now! Certificates are available to those with release secrets access @ https://github.com/nodejs/secrets/tree/master/build/release
• Allocate new server(s)
  • 104.131.173.199, an 8G DO server to get us started, it's been assigned new.nodejs.org for now
• CDN
  • We are discussing an association with CloudFlare to front nodejs.org, this obviously puts less load on the server so we don't need to go overboard. Will keep everyone informed on how that's going and try and get other members of the build team access to the config so we can play & understand what's involved
• DNS
  • Currently the DNS pointers go to Joyent, unfortunately it's not in a form that can be managed from outside of Joyent so we'd like to move this. If we go with CloudFlare for CDN then in order for them to serve the apex (nodejs.org) then they'll need to also control the DNS. They have a nifty API for DNS control so it might be nearly as good as using Route53.
• Server config
  • We need to merge nodejs.org with the current iteration we have @ iojs.org, this is obviously a non-trivial task if we want as little disruption to users as possible. I'd like us to serve both nodejs.org and iojs.org from the same server if we can get CDN set up for at least nodejs.org.
  • WIP WIP: config for new nodejs.org server #162
• Make all iojs.org/dist/ and nodejs.org/dist/ files available from the new server
• New release procedure to unify Node.js releases and io.js releases from the same repo to the same server but different distribution directories

/cc @nodejs/website

[mikeal]

The versions.json file we're using only has io.js releases in it. It would be good to know what the unified json file will look like so that we can test it.

https://github.com/nodejs/new.nodejs.org/blob/master/source/versions.json

[rvagg]

doing that right now!

[mikeal]

awesome :)

[rvagg]

💥 all done