Question: Where do I add exactly the CNAME?
See original GitHub issueThe instructions say: You can configure a custom domain with GitHub Pages by adding a CNAME file to the public/ folder.
I tried adding the public folder to my repo’s root and to src, folder, but there’s no CNAME in my build folder still… what’s the correct place for it?
Issue Analytics
- State:
- Created 7 years ago
- Comments:11 (8 by maintainers)
Top Results From Across the Web
Adding a CNAME Record | Name.com
Select CNAME in the Type drop-down menu. · Enter the subdomain in the Host field (usually www). · Enter the domain/value in the...
Read more >How to set up a CNAME record for a custom domain name
You only need to organise a CNAME record to be set up if you would like your site to appear at a subdomain...
Read more >How to Create a CNAME Record For Your Domain
- Having logged into the Namecheap account, go to your Domain List -> click "Manage" next to the domain -> the "Advanced DNS"...
Read more >What's a CNAME record? - DNSimple Help
A CNAME record must always point to another domain name, never directly to an IP address. DNSimple's record editor will warn you if...
Read more >Add a CNAME record to your domain's DNS records
You'll add the CNAME record to your domain's DNS records that are stored with your domain host. To add the record yourself, follow...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@Timer thank you very much! That indeed did the trick. In case anyone else needs to see an example https://github.com/torontojs/torontojs.com/tree/gh-pages
The other required step (for me) was updating my
homepage
key toI see. The issue is that in 0.5.0 we had a breaking change, which introduce the
public
folder (detail).Please update your react-scripts. You can follow the migration guide to keep your current code base, one by one. You can also re-init a new app and move your code base there, but it is not really safe. Do the migration is a lot safer.