Skip to content

Is www still needed, and if so what should its role be? #4488

Open

Description

@sxa

This was discussed in a recent build workgroup call. Do we still need the www server? It was originally set up to serve downloads of Node.js and the website. The website is now on Vercel and downloads are staged on the www server during the release process but hosted on R2 for public access. This may mean that the server we refer to as www could be replaced, although as a backup of our release artefacts it may still have some value.

Thoughts can be added into this issue. We should clarify exactly what it being used for in case some use cases have not been captured in the above introduction and use that to determine precisely what would be required by any replacement system.

Related issues:

Activity

  1. richardlau commented on Sep 28, 2026

    @richardlau
    Member

    It still:

    • Checks (cron) to see if the nightly and v8-canary HEAD commits and trigger Jenkins builds if they have changed.
    • Automatically promote (cron) nightly builds.
    • Stage release builds. Release process has the releasers ssh into the machine to download the SHASUMS, sign locally and then re-upload as part of the promotion script.

    There's also a metrics script being run by cron that I have no idea whether is being used by anything or a relic of pre-CloudFlare proxying.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions