Hey!
Just starting to get my feet wet with contributing to this project.
How is the site being hosted? It seems to be a server configuration error.
I believe the url is nodejs.dev not staging.nodejs.dev. Still the server could be configured to redirect any subdomain.
Looks like the /preview pages are hosted from subfolders. Nice!
What would you want the root path to display anyways?
@jemjam what timing
I finally got to just putting a placeholder that redirects to the repo
src -> https://github.com/MylesBorins/staging.nodejs.dev
The staging site for previews is just a GCS bucket fronted by cloudflare. We don't currently maintain a staging branch, so I don't think it makes a ton of sense to have anything too complicated there. We could vendor in the HTML I provided and automate some CD around deploying updates (all the infrastructure to do that is in this repo)... but I think if we want to regularly put an entire build of the website in the root regularly we might want to rethink some of the strategy for builds (and our retention policy in the bucket).
The bucket is managed in a nodejs GCP project which I could invite folks too, although it is currently setup to my credit card so I may want to hand it off the the foundation before adding more folks (currently running on credits).
@MylesBorins staging has the old content of the website note the logos near the bottom.
@benhalverson I'll rephrase 馃槄
the staging.nodejs.dev bucket doesn't have anything at the root. The staging deploy script has been off for a bit and afaict the branhch hasn't had a publish in months.
The data retention policy of staging.nodejs.dev automatically deletes resources after 60 days.
I think this can be closed now. I like the Lost? button @MylesBorins
Most helpful comment
@jemjam what timing
I finally got to just putting a placeholder that redirects to the repo
https://staging.nodejs.dev/
src -> https://github.com/MylesBorins/staging.nodejs.dev
The staging site for previews is just a GCS bucket fronted by cloudflare. We don't currently maintain a staging branch, so I don't think it makes a ton of sense to have anything too complicated there. We could vendor in the HTML I provided and automate some CD around deploying updates (all the infrastructure to do that is in this repo)... but I think if we want to regularly put an entire build of the website in the root regularly we might want to rethink some of the strategy for builds (and our retention policy in the bucket).
The bucket is managed in a nodejs GCP project which I could invite folks too, although it is currently setup to my credit card so I may want to hand it off the the foundation before adding more folks (currently running on credits).