Add plumbing to upload schemas to GitHub Pages every day - #4727

cc @madskristensen

This is great

Great, merging

@madskristensen The action fails:

Error: Get Pages site failed. Please verify that the repository has Pages enabled and configured to build using GitHub Actions, or consider exploring the `enablement` parameter for this action. Error: Not Found - https://docs.github.com/rest/pages/pages#get-a-apiname-pages-site
Error: HttpError: Not Found - https://docs.github.com/rest/pages/pages#get-a-apiname-pages-site

Adding GitHub action as a deployment source should fix it,.

@hyperupcall Done!

@madskristensen Awesome! It works.

Is there anything else that I can do to prep for closing #4695? Or is it just a matter of updating DNS records?

@hyperupcall is there a URL for the GH Pages site? I'll see if I can redirect the DNS, but I think we need to update the schema URLs in the catalog to point to the GH location instead of schemastore.org. If not, we lose the HTTP redirection. We can then move them to a schemastore.org URL once the DNS has been updated. Thoughts?

@madskristensen Yup, the GitHub pages schemas can be accessed like https://schemastore.github.io/schemastore/ava.json. I also created an index.html, so there is a homepage, but um I think that was a mistake and I'll replace that with a HTTP redirect to https://www.schemastore.org/json/.

I'll see if I can redirect the DNS, but I think we need to update the schema URLs in the catalog to point to the GH location instead of schemastore.org. If not, we lose the HTTP redirection. We can then move them to a schemastore.org URL once the DNS has been updated. Thoughts?

That sounds great. I created #4759 that does just that,.

@hyperupcall there are still a bunch of references to json.schemastore.org in catalog.json. They will break due to the lack of subdomain redirection. If we move those to raw.githubusercontent.com, then it won't break during the transition.

When we map the subdomain json.schemastore.org then we need a redirection rule somewhere such that https://json.schemastore.org/appveyor will resolve to the right path for https://raw.githubusercontent.com/SchemaStore/schemastore/refs/heads/master/src/schemas/json/appveyor.json. Do you know how to create that redirection rule @hyperupcall?

DNS is now moved for schemastore.org and www.schemastore.org. There is no styling on the site, since only the index.html file is written. Could we create the website folder with all the assets (png, js, css) and then copy that entire folder in cli.js?

@madskristensen

When we map the subdomain json.schemastore.org then we need a redirection rule somewhere such that https://json.schemastore.org/appveyor will resolve to the right path for https://raw.githubusercontent.com/SchemaStore/schemastore/refs/heads/master/src/schemas/json/appveyor.json. Do you know how to create that redirection rule @hyperupcall?

In cli.js, in the task that generates the website for GitHub pages for the file ./src/schemas/json/appveyor.json, it creates both a ./website/appveyor.json and a ./website/appveyor file. This matches the previous behavior where accessing both https://json.schemastore.org/appveyor and https://json.schemastore.org/appveyor.json returns the Appveyor json schema. Is there something I'm missing or does this address your comment?

DNS is now moved for schemastore.org and www.schemastore.org. There is no styling on the site, since only the index.html file is written. Could we create the website folder with all the assets (png, js, css) and then copy that entire folder in cli.js?

Noted, I made the fix for that in #4766

@hyperupcall excellent work on this!

Is there something I'm missing or does this address your comment?

I missed that part. I've now updated DNS CNAME entry to point to this new location. Once it propagates, we should see it working

@hyperupcall the DNS is now fully propagated (for my location at least) and everything seems to work correctly. Traffic to the old host is plummeting rapidly and will be zero in a matter of hours, I believe. This was a well executed project. Thank you so much for your effort.

...now the json.schemastore.org subdomain isn't working. This is not easy nor well documented by GitHub.