Commits remove CNAME file of custom domain #5341
-
I have recently updated to Quarto 1.3 but it seems is creating problems when I am trying to deploy my blog. I am using Github pages and for deployment, I am just using the publish command in the terminal. I have found out that after I start using Quarto 1.3 the process for deployment seems to be erasing the CNAME file needed for the custom domain: This is causing Github to also revert back to the default url, and not my custom domain. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 9 replies
-
I think this is likely what you're looking for: If you move your CNAME file next to your resources:
- CNAME It will be copied to the output directory when you build your website. |
Beta Was this translation helpful? Give feedback.
-
I did and the problem persists. Here is the link to my repo in case it helps. It clearly there is something that happens in the background and changes the url. |
Beta Was this translation helpful? Give feedback.
-
I don't see a CNAME file checked into the root of your repository. If this isn't working / you want some advice from others that are a bit more familiar with GitHub Pages than I am, I think the discussion I linked to would be a good place to start / post additional follow up questions. |
Beta Was this translation helpful? Give feedback.
I think this is likely what you're looking for:
#3249
If you move your CNAME file next to your
_quarto.yml
file and add it as a resource:It will be copied to the output directory when you build your website.