Skip to content
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
Open
@Trott

Description

@Trott
Member

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

WaleedAshraf commented on Jul 22, 2018

@WaleedAshraf

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

refack commented on Jul 22, 2018

@refack

+1

Trott

Trott commented on Jul 22, 2018

@Trott
MemberAuthor

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

Trott commented on Jul 22, 2018

@Trott
MemberAuthor

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

bjb568

bjb568 commented on Jul 22, 2018

@bjb568

Shouldn’t it just be a 301 redirect?

maclover7

maclover7 commented on Jul 22, 2018

@maclover7

+1, cc @rvagg for Cloudflare bits

WaleedAshraf

WaleedAshraf commented on Jul 22, 2018

@WaleedAshraf

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

Trott

Trott commented on Jul 22, 2018

@Trott
MemberAuthor

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

refack commented on Jul 24, 2018

@refack

@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

mhdawson commented on Jul 30, 2018

@mhdawson
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.

5 remaining items

Loading
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @refack@rvagg@Trott@maclover7@bjb568

        Issue actions

          redirect to nodejs.org · Issue #432 · nodejs/iojs.org