You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using a custom domain, Github requires a CNAME file. I think this can be done through correct merging of old and new gh-pages branches, but if I understand correctly, ember github-pages:commit will destroy the branch and recreate it, removing any CNAME file that's committed to the branch. Use git push origin gh-pages:gh-pages -f with caution for this reason. Not sure if this is an issue with this add-on, but it's worth noting.
The text was updated successfully, but these errors were encountered:
allthesignals
changed the title
Custom Domain
Custom Domain Configuration Overwritten
Aug 2, 2016
NOTE I could resolve the issue by putting the CNAME file in the "public" folder. Then GitHub automatically recognizes and sets the custom domain, even in the Settings UI
I wanted to add my custom domain. I did it in the GitHub interface but then stupidly did a pull (as the CNAME creation commit was from the Github web UI) on my code, which "destroyed" the whole local code. As this add-on is merging many files and not leaving much on the master branch which is online, I thought creating the CNAME locally in my project files would do it, but no... The CNAME file is not being pushed to the remote master.
Any ideas?
When using a custom domain, Github requires a CNAME file. I think this can be done through correct merging of old and new gh-pages branches, but if I understand correctly,
ember github-pages:commit
will destroy the branch and recreate it, removing any CNAME file that's committed to the branch. Usegit push origin gh-pages:gh-pages -f
with caution for this reason. Not sure if this is an issue with this add-on, but it's worth noting.The text was updated successfully, but these errors were encountered: