Complete Git Guide: Understand and Master Git and GitHub - Configuring a Custom Domain for GitHub Pages

This tutorial covers deploying a React application using GitHub Pages, setting up a custom domain, and troubleshooting common issues. It guides through DNS configuration, rebuilding the app, and verifying the setup. The video also demonstrates updating the application and ensuring it reflects changes online. Finally, it concludes with a preview of creating GitHub Pages using built-in markups.

What is the primary purpose of using GitHub Pages for a React application?

• To build a mobile application

• To create a private repository for code collaboration

• To host a static website directly from a GitHub repository

• To manage DNS settings for a domain

What is required to use a custom domain with GitHub Pages?

• A paid GitHub subscription

• A personal domain name

• A specific GitHub Pages theme

• A GitHub Enterprise account

Which DNS record type is used to point a custom domain to GitHub Pages?

• TXT record

• CNAME record

• MX record

• A record

What issue might occur when using a custom URL with GitHub Pages?

• The repository may become private

• The domain may expire

• The website may not load due to resource path errors

• The GitHub account may be suspended

How can you resolve a 'not found' error for resources on a custom domain?

• By changing the GitHub repository name

• By updating the GitHub Pages theme

• By rebuilding the application with the correct homepage URL

• By clearing the browser cache

What command is used to deploy a React application to GitHub Pages?

• npm start

• npm run build

• npm run deploy

• npm install

What should be verified after re-deploying a GitHub Pages application?

• The local development server

• The repository's README file

• The GitHub account settings

• The custom domain configuration

Why might the custom domain configuration reset after a push to GitHub Pages?

• Because of a GitHub server outage

• Due to a bug in the GitHub Pages script

• Because the repository is private

• Due to incorrect DNS settings

What is a potential solution if the custom domain resets after updates?

• Stop using a custom domain

• Use a different GitHub account

• Manually reconfigure the custom domain each time

• Switch to a different hosting provider

What is the final step to ensure the custom domain is correctly configured?

• Verify the DNS settings in the domain registrar

• Check the GitHub Pages theme settings

• Ensure the repository is public

• Update the GitHub account password