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
GitHub actions seems to remove CNAME from pages settings and 404s #53
Comments
👋 from the Pages team. I was checking out your project and noticed this, so thought I'd offer a suggestion. It's now possible to use Actions as the source, which allows you to have more control over the build. This option also removes the requirement for a CNAME file to exist, and you can deploy from any branch to Pages. Happy to open a PR with an starter workflow to set this up if you like. |
Hey @tcbyrd welcome to the Aurae project. Hope you love it here! Feel free to start a pull request for us, we would love to use whatever best practices you suggest. I think in general myself and the others working on the project aren't the most experienced with Pages or Actions, so any clues and contributions would be amazing. |
Also relevant to note that changing the #56 👀 |
Another related issue about helping myself and the maintainers keep an eye on things if the build breaks and the website goes down. #82 |
So the website has been down all morning. I checked the pages settings and it looks like the page settings had been reversed? All of our GitHub pages configuration was lost. https://github.com/aurae-runtime/aurae/settings/pages I had to to back to the settings and re-enable the pages integration, select a branch, and re-enter the custom domain name. Waiting to see if the website comes back online. |
Upon merging a PR to main (or committing directly to the branch because I am a horrible person) a GitHub action is kicked off to update the static site using GitHub pages. Shortly after the event, the website aurae.io will return a 404.
Looking in the get GitHub pages settings for the repository the domain name value is unexpectedly missing.
Setting the value back to
aurae.io
fixes the 404 and the site is now updated with the most recent changes from themain
branch.The text was updated successfully, but these errors were encountered: