Hot answers tagged

4

Since it based on rendering plain files from a git repository, I don't think you can use dynamic information. The goals of Github Pages is to show a static site easily from an open source project. You can still contact them and I think you have a dedicated support if you use Github Enterprise.


4

As covered here, GitHub Pages is served with Nginx and automatically gzip's content. You can confirm gzip compression for your site by checking the HTTP headers with online tools like this one. Enter the URL to a webpage or resource, and type in gzip under "Accept-Encoding" to indicate that the HTTP client (i.e., the online testing tool in this case) ...


4

If the DNS has started to propagate, you may be facing caching on your computer or ISP's DNS server. I'd wait for a bit, or try either: temporarily using a different DNS provider, e.g. OpenDNS or Google Public DNS (you may need to restart your browser or OS) checking from a computer using a different ISP/DNS server Good luck.


3

To make use of a certificate you not only need to have your own domain and certificate but you need to have access to the server configuration so that you actually could use the certificate. In case of github you don't have such deep access so you cannot make use of any certificate, no matter if you got it through Let's Encrypt or some other CA.


3

Ideally, no. It is very, very difficult to get penalised (Sandboxing, Deindexing). Having duplicate content may 'de-value' your content and it will have less weight than it would organically but it's Google's job to identify the original content whilst devalueing other pages. Setting a canonical link on your website is your way of telling search engines ...


3

AFAIK unless somethings changed you arent able to use Namesevers as they are used for the main domain, you will have to use a A domain or a CNAME to cover the domain. Sorry to break the news to you.


3

Do I use a CNAME for www only then, with no A record at all? You would need to use a CNAME for the www.example.com subdomain, and an ALIAS record for your root domain example.com (aka., "apex domain"). As indicated in the help document you provided on Setting up a custom domain with Pages: Some DNS providers (like DNSimple) allow you to use an ...


3

This question is opinion-based but I'd still like to help you out here. Advantages: Well, it's free! GitHub's CMS gzip & minify A fast CDN Disadvantages: No 'good' cache No 'good' SSL support No good cookies system Of course, Github pages is free so I imagine there has to be downsides. I understand you're thinking that but GitHub pages is ...


3

You have forgotten to set your custom domain value at production_url (see _config.yml).


2

From what I can see, gist.github.com uses javascript to embed gists such as: <script src="https://gist.github.com/1234.js"> </script> And although Google parses some javascript but I doubt 3rd party widgets would get parsed (see update below) but this exact issue was discussed by Simon Bingham here. He suggests you use the "SEO Friendly ...


2

According to https://help.github.com/articles/tips-for-configuring-an-a-record-with-your-dns-provider/#configuring-a-www-subdomain If you configure both an apex domain (e.g. example.com) and a matching www subdomain (e.g. www.example.com), GitHub's servers will automatically create redirects between the two. Here is my setup that seems to work ...


2

The problem is that Google hates pages in the sitemap that do any kind of redirect. So, try something from this few options that crossed my mind: Don't let the page in the sitemap to redirect (the pages must give status code 200 - OK) Change the pages in the sitemap with the landing pages. Exclude redirect pages in sitemap.


2

The tracking code on its own is not a security risk. Remember, anyone can see this simply by viewing the HTML source of your website. If you're putting your website code on Github because you think other people could use it, you shouldn't include your tracking code because you don't want their visitors to be logged to your account.


1

I just received an answer from the GitHub support: "GitHub Pages will sometimes respond with 302 Found redirects when you have A records set up for an apex domain. It's part of our DDoS mitigation system for GitHub Pages sites." My problem is that my domain hoster doesn't support DNS CNAME Records, so I think that I have to deal with what I have.


1

You can forward or redirect your domain. Redirect type 301 (Permanent) — Redirects to the site you specified in the Forward To field using a "301 Moved Permanently" HTTP response. The HTTP 301 response code tells user-agents (including search engines) that the location has permanently moved. 302 (Temporary) — Redirects to the site you specified in the ...


1

After doing some research, turns out I am not the only person with this issue. The solution was to change my GitHub CNAME file from non-www to www., looks like sending someone without the www was causing the time to first byte to be extra long. I'm still looking into the reason why.


1

Most likely caused by your TTL values or DNS not propagating. Time to live is what dictates how long it will be until your computer refreshes its DNS related information. For example, the IP address your domain name points to or where your MX records are directing email. This time is defined in seconds and the default setting can be found in ...


1

Well, 404 should be used when the resource do not exist, is not that you're not authorized, it is not there at all. 403 should be for forbidden resources, regardless you're authenticated, you might not have permission over a given resource. I rather 401 for resources that are found but requires some sort of authentication to get it. IMO


1

Personally I think this is justified. By returning a 403 instead, Github would be confirming that a repository with that name exists, which in itself could be seen as a security hole (or at least undesirable). As a contrived example, imagine that these repositories existed: http://github.com/valve/HalfLife http://github.com/valve/HalfLife2 If one day ...


1

Yes, it is possible. Download the publish profile - Click this link to download your publish profile for your website. The publish profile contains your credentials (user name and password) and the URLs for uploading content to your website with FTP and Git. The profile file is in XML format and can be viewed in a text editor. Set up ...


1

It requires two things; Add a file called CNAME at the root of the project which only contains the domain name, see the docs In your DNS server, add an entry. This is done at your domain name service provider, or named/bind zone file Follow the instructions on setting up a custom domain with GitHub pages


1

For github projects, you can subscribe to the release tag for project via RSS. Some examples: https://github.com/dropbox/dropbox-js/tags.atom https://github.com/angular/angular.js/tags.atom


1

Breno Salgado posted this simple Jekyll plugin on StackOverflow: ./_plugins/markdown_tag.rb: module Jekyll class MarkdownTag < Liquid::Tag def initialize(tag_name, text, tokens) super @text = text.strip end require "kramdown" def render(context) "#{Kramdown::Document.new(File.read(File.join(Dir.pwd, '_includes', ...


1

Other people have commented on the instructions that they have had similar problems. One person found that it was a type on the domain name that caused the problem: My name is 2DD847, and for the domain, I thought it doesn't depend on capital or lower letters. Now I changed the repo to capital letters and it works. Check your domain names and make ...


1

GitHub allows you to create a custom 404 page but there is a caveat. The 404 will be displayed only if you use a custom domain or for user pages. Custom 404s only work when they are served from the root of a Pages domain, for example a project using a custom domain or a user pages repository. A custom 404 page on project pages that are not using a custom ...


1

According to the GitHub documentation on custom 404s you are out of luck: Custom 404s only work when they are served from the root of a Pages domain, for example a project using a custom domain or a user pages repository. It looks like sub-folders are not supported. Only the root folder.


1

Here is the relevant help page: https://help.github.com/articles/user-organization-and-project-pages They have two types of pages: User/Organization Pages and Project Pages Based on this, they are not limiting the use of Github Pages to just software projects. They allow pages for users and organizations.


1

I eventually gave in and solved this with a Apache config redirect (although I wanted to do it with pure DNS it looks like this is not possible...) <VirtualHost *:80> DocumentRoot /www/html/firstdomain.com ServerName firstdomain.com RedirectMatch 301 ^(.*)$ http://seconddomain.com$1 ErrorLog logs/firstdomain.com-error_log TransferLog ...


1

See Fork a repo / Clone your fork.



Only top voted, non community-wiki answers of a minimum length are eligible