Skip to content
This repository has been archived by the owner on Nov 21, 2018. It is now read-only.

redirect to nodejs.org #432

Open
Trott opened this issue Jul 22, 2018 · 11 comments
Open

redirect to nodejs.org #432

Trott opened this issue Jul 22, 2018 · 11 comments

Comments

@Trott
Copy link
Member

Trott commented Jul 22, 2018

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

@WaleedAshraf
Copy link

Would it better to show this message before redirecting?

io.js has merged with the Node.js project.
There won't be any further io.js releases. All of the features in io.js are available in Node.js v4 and above.
Redirecting to nodejs.org.

@refack
Copy link

refack commented Jul 22, 2018

+1

@Trott
Copy link
Member Author

Trott commented Jul 22, 2018

Would it better to show this message before redirecting?

@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
Copy link
Member Author

Trott commented Jul 22, 2018

@refack Any chance we can do this via a DNS change and some hopefully-trivial Cloudflare configuration?

@bjb568
Copy link

bjb568 commented Jul 22, 2018

Shouldn’t it just be a 301 redirect?

@maclover7
Copy link

+1, cc @rvagg for Cloudflare bits

@WaleedAshraf
Copy link

@Trott Sound fine to me. 👍
Thanks for the details.

@Trott
Copy link
Member Author

Trott commented 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
Copy link

refack commented Jul 24, 2018

@refack Any chance we can do this via a DNS change and some hopefully-trivial Cloudflare configuration?

Should be.

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.

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
Copy link
Member

+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.

@rvagg
Copy link
Member

rvagg commented Nov 21, 2018

Redirect got activated today.

/download, /dist, /docs and /api remain intact but everything else goes to https://nodejs.org/

I'm going to archive this repo now. I don't see objections.

End of an era, it was fun.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

7 participants