Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Staging.nodejs.dev does not display anything #790

Open
designMoreWeb opened this issue Jul 16, 2020 · 6 comments
Open

Staging.nodejs.dev does not display anything #790

designMoreWeb opened this issue Jul 16, 2020 · 6 comments
Labels

Comments

@designMoreWeb
Copy link

@designMoreWeb designMoreWeb commented Jul 16, 2020

I visited our homepage and i got the following error.
Screenshot 2020-07-16 at 2 28 55 PM

@benhalverson benhalverson changed the title Stagging.nodejs.dev does not display anything Staging.nodejs.dev does not display anything Jul 16, 2020
@corinty
Copy link

@corinty corinty commented Aug 10, 2020

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.

@NYCJacob
Copy link

@NYCJacob NYCJacob commented Aug 11, 2020

I believe the url is nodejs.dev not staging.nodejs.dev. Still the server could be configured to redirect any subdomain.

@jemjam
Copy link

@jemjam jemjam commented Aug 12, 2020

Looks like the /preview pages are hosted from subfolders. Nice!

What would you want the root path to display anyways?

@MylesBorins
Copy link
Member

@MylesBorins MylesBorins commented Aug 12, 2020

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

@benhalverson
Copy link
Contributor

@benhalverson benhalverson commented Aug 12, 2020

@MylesBorins staging has the old content of the website note the logos near the bottom.

@MylesBorins
Copy link
Member

@MylesBorins MylesBorins commented Aug 12, 2020

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
6 participants
You can’t perform that action at this time.