Don't build/serve website from NGINX
MattIPv4 opened this issue · comments
The website is now served from Vercel, so it is redundant to serve it from NGINX as well. It has also been observed that the version from NGINX that is available at origin.nodejs.org is being indexed in Google, so removing it should resolve this.
It should be called out that the dist
, download
, docs
, api
, etc. should still be served from NGINX.
The site build script can be removed, as well as various parts of the NGINX config relating to the serving of Next.js:
build/ansible/www-standalone/resources/config/nodejs.org
Lines 114 to 117 in 0a0ed87
build/ansible/www-standalone/resources/config/nodejs.org
Lines 124 to 172 in 0a0ed87
build/ansible/www-standalone/resources/config/nodejs.org
Lines 264 to 292 in 0a0ed87
build/ansible/www-standalone/resources/scripts/build-site.sh
Lines 7 to 8 in 0a0ed87
build/ansible/www-standalone/resources/scripts/build-site.sh
Lines 23 to 26 in 0a0ed87
I'm probably missing some other bits.
The first thing I can do is delete the website contents from the server. It's outdated now anyway. @nodejs/build-infra wdyt?
👍 Not build infra, but removing the site content seems like a good first step and would solve for the Google indexing issue (and act as a confirmation we don't need it before removing all the code/config for building/serving it).
I moved all website files to a folder at /home/www/nodejs_old
in case we need to recover something, and updated the robots.txt to disallow everything.
Remains:
$ ls nodejs
robots.txt traffic-manager
$ cat nodejs/robots.txt
User-Agent: *
Disallow: /
Opened #3641 to remove the build scripts and webhook.