This repository was archived by the owner on Nov 21, 2018. It is now read-only.
This repository was archived by the owner on Nov 21, 2018. It is now read-only.
redirect to nodejs.org #432
Open
Description
It's probably about time to redirect https://iojs.org to https://nodejs.org and then archive this repository. Any objections?
/ping @nodejs/build @nodejs/website @nodejs/tsc @nodejs/community-committee
Activity
WaleedAshraf commentedon Jul 22, 2018
Would it better to show this message before redirecting?
refack commentedon Jul 22, 2018
+1
Trott commentedon Jul 22, 2018
@WaleedAshraf That would work, but my (mild) preference would be not do that. That message has been on the iojs.org website for over 2 years. I could be wrong, but at this point, I don't think anyone will be especially helped by that message compared to simply having to infer meaning from the experience of "I went to iojs.org and got redirected to nodejs.org."
Given how little attention this repo has gotten (it's build step
npm run gulp
fails in Node.js 8.x and above, and that's just for starters), I'd rather just update the DNS record than having to maintain this repo longer for the sake of a message that few will see and even fewer will benefit from.Trott commentedon Jul 22, 2018
@refack Any chance we can do this via a DNS change and some hopefully-trivial Cloudflare configuration?
bjb568 commentedon Jul 22, 2018
Shouldn’t it just be a 301 redirect?
maclover7 commentedon Jul 22, 2018
+1, cc @rvagg for Cloudflare bits
WaleedAshraf commentedon Jul 22, 2018
@Trott Sound fine to me. 👍
Thanks for the details.
Trott commentedon Jul 22, 2018
Interestingly, if I browse to the current IP address of www.iojs.org (138.197.224.240), it already redirects to www.nodejs.org. So this is already partially setup somewhere.
refack commentedon Jul 24, 2018
Should be.
AFAIK they are served from the same server who's default "virtual server" is the nodejs.org site, so a direct IP URL will get redirected.
P.S.
https://github.com/nodejs/build/blob/f62cbf66b32d69b4adb3c02292c627b753a3710a/setup/www/tasks/nginx.yaml#L1-L12
mhdawson commentedon Jul 30, 2018
+1 to redirect. @rvagg any objections? If not unless you can think of a reason we should do something else updating the cloudlfare config as suggested sounds the easiest. If we are agreed I can probably take a look at that.
nodejs/iojs.org
inGOVERNANCE.md
? nodejs/nodejs.org#18295 remaining items