![]() ![]() Note: If you already have a www CNAME record, you can edit it to point to your GitHub Page. ![]() You will see a few A records, some CNAME records, and some MX and NS records (not important for now).Ĭreate a new CNAME record with So your record will look something like this. There will be some of the default record there already. You will be brought to a table of records. Change your “Custom Domain” to Now login to your GoDaddy account, and navigate to “Domains > Manage DNS”. Go your GitHub respository, go to “Settings > GitHub Pages”. The request will follow the resource that the records points to and continue to resolve the request from there. Unlike the A record, the CNAME need not be an IP address, it can point to a domain or a subdomain. This allows you to point different subdomains to different parts of the web. The second type of record CNAME (canonical name), is also known as the alias. But for the IP address, there isn’t any top level domain to resolve, hence, there is no need for the trailing. Note that in the host section, there is a trailing. Your record will look something like this: Let’s assume your home computer has the IP address 192.168.0.1. For example, you could have point to your home computer and serve files out of there. A RecordĪn A (address) record directs the hostname to a certain IP address. No idea what I am talking about? Read on. Here, I cover the A record and CNAME record, which is used in pointing your domain to a certain resource online. These records will point to different resources, then your request will be passed from one resource to another and finally be resolved to an IP address. There are a few different types of DNS records. Examples would include, (see GitHub uses subdomains too). These are one level down the apex domains, and are usually used to split up your sites into different parts. These are one level below the top-level domain (. Types of domainsīefore that, let’s cover the few types of domain that GitHub supports. Instead, I am going to just cover a simple version of it, covering what we will be using in this post. If covered in detail, this section can take a whole posts by itself. If you go on and see the files available (in the “code” tab), you will see the index.html sitting there, waiting to be shown to the world. What you have just done is to create a new branch master in your respository and populate it with the generated page. Choose a nice layout and save the changes. This generator lets you edit the information to your page. Go on and “launch automatic page generator”. Scroll all the way down to the section where it says “GitHub Pages”. Note: Your new repository must have the following name. If you have no idea what I am talking about, read on.Ĭreate a new repository, then go on to the “settings” tabs of your repository. If you already have your content ready on that repository, you can skip this section. Setting up a page on githubĮach account on GitHub will be allowed one subdomain in the following format. If everything goes well, you can expect a tutorial on how to setup a blog on there, complete with google analytics and all that. I have plans to migrate my blog to my github account. You can focus on your content, push it to GitHub, and it will be “compiled” automatically. Plus, using GitHub Pages means that you can take advantage of the Jekyll generator. Have the content ready, push it to GitHub, and it will be deployed to GitHub Pages. Using GitHub Pages fits into my workflow. The reason why I chose Github Pages is because of my extensive usuage of Github in general for project hosting. ![]() TLDR: Skip the explanation and go straight to the steps But still, this tutorial will make a good read □ If you don’t already have one, you might not be able to really try this out for yourself. Note: This tutorial requires you to have a domain. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |