Redirect old docs to new docs

[papb]

I think we should add a 301 REDIRECT (Moved Permanently) to the old v3 docs and the "old" v5 docs pointing to the new hosts instead (here and here respectively).

This would solve sequelize/sequelize#10610 as well

@sushantdhiman

[sushantdhiman]

We can redirect old v5, not access to old v3 docs

[papb]

@sushantdhiman Who has access to the old v3 docs?

[sushantdhiman]

Old v5 docs redirected to new ones

[papb]

@sushantdhiman Are the old v3 docs (here and here) completely inaccessible? Isn't there anything we can do about them?

[sushantdhiman]

@janmeier / @sdepold

[sushantdhiman]

By the way https://sequelize.readthedocs.io/en/v3/ will get redirected to https://sequelize.org/v3

[papb]

@sushantdhiman Actually apparently only the main page follows the redirect.

Entering one specific page such as http://docs.sequelizejs.com/manual/associations.html does not redirect...

Also will these redirects affect SEO?

[joequincy]

It looks like this is in progress... visiting a page like https://docs.sequelizejs.com/en/latest/docs/associations/ (Google points here) appropriately redirects to https://sequelize.org/master/manual/associations.html

However, the current cert served for https://docs.sequelizejs.com/* is assigned for *.surge.sh, which causes browser warnings in at least Chrome and Firefox, e.g.

Additional cert screenshots for troubleshooting

[papb]

@joequincy Indeed I was able to reproduce this, @sushantdhiman can you take a look?

[sushantdhiman]

We can't fix docs.sequelizejs.com, that's why I got new domain sequelize.org

[github-actions]

This issue has been automatically marked as stale because it has been open for 7 days without activity. It will be closed if no further activity occurs. If this is still an issue, just leave a comment or remove the "stale" label. 🙂

[sdepold]

I guess this ticket is done @ephys ?

[sdepold]

So this works now https://sequelize.readthedocs.io/en/v3/.

[ephys]

I guess this ticket is done @ephys ?

Yep! Looks good :)