vento.js.org

[kwaa]

• There is reasonable content on the page (see: No Content)
• I have read and accepted the Terms and Conditions

[MattIPv4]

Hi there!

❌ Before we can accept your domain request, you need to create a file named CNAME in the root of your github pages site (this may not be the root of your repository). 📝
This file should contain a single line with the full js.org domain you are requesting, in this instance vento.js.org.

[indus]

I've already added your requested subdomain to JS.ORGs zonefile. But like Matt said the CNAME is missing. As you are using a workflow to deploy the page there may be other steps involved to get the CNAME working. FYI: #7853 (comment)
I'll merge after we have "contact". Please keep this PR open.

[kwaa]

@oscarotero Looks like CNAME doesn't work. can you take a look?

Perhaps deploying from artifacts is different from the common branching method and needs to be modified in Repo Settings.

[oscarotero]

I just changed the custom domain in the GitHub Page settings. I hope it works well now.

[MattIPv4]

It looks like there is a redirect loop?

curl -I https://vento.js.org/
HTTP/2 301 
date: Sun, 02 Jul 2023 17:02:50 GMT
content-type: text/html
content-length: 162
location: https://vento.js.org/
x-github-request-id: 0E38:8616:29A51CA:2B00B60:64A1AD8E

This looks to be a similar issue to previous folks we've seen using GitHub's new Pages deployment. Might I suggest you reach out to GitHub support to see what's going on? They appear to have broken something with this new method. Feel free to cc me (mattipv4@js.org).

[kwaa]

@oscarotero Maybe I can modify the current actions to push to the gh-pages branch to avoid this problem?

[oscarotero]

I finally got it to work following this comment #7853 (comment)

I set the classic deploy option (from branch) and then set again to GitHub action mode. This seems to fix the issue.

https://vento.js.org/