4 ms·

I use Namecheap DNS (free, as they are my registrar). I can control everything, including APEX. It has never fail me. And for hosting, Github pages (Jekyll roc

I use Namecheap DNS (free, as they are my registrar). I can control everything, including APEX. It has never fail me. And for hosting, Github pages (Jekyll rocks!) do a great job. I think you are still paying too much, Paul.

timrivera 13y ago
That's what I immediately thought when I first read it, especially now that Github Pages are served over Fastly's CDN [1]. Then I realized that Github Pages do not support server side (301) redirects at all. Quite a big turn-off when you move an existing website over a new platform. [1] https://news.ycombinator.com/item?id=7019148 https://news.ycombinator.com/item?id=7019148, https://news.ycombinator.com/item?id=6975830 https://news.ycombinator.com/item?id=6975830
itafroma 13y ago
> And for hosting, Github pages (Jekyll rocks!) do a great job. Using GitHub pages to auto-build your Jekyll site is great if and only if you have no need to customize your Jekyll build or website environment: - You must use the versions deployed by GitHub; most of the time they're up to date, but if there's a bug fix you're relying on in any of the libraries, you're out of luck. I ran into this on my own site: RedCarpet had a Markdown parsing bug that was fixed in version 3, but the Jekyll that GitHub Pages uses depends on version 2. Jekyll loosened this dependency weeks ago, but it's not in a full release yet. - You can't use any Jekyll plugins, even the ones marked safe. You can avoid the above by building your site locally and uploading the output, there are still a few other caveats: - Like timrivera mentioned, there is no support for server-side redirects outside the baked-in ones (i.e. www to or from naked domain; name.github.io to domain). S3 has these out of the box. - You can only use one domain per GitHub Pages repository. - GitHub will allow Googlebot to index your repository's master branch. If you're used to that convention, you're out of luck: it's hardcoded into github.com's robots.txt. You need to use a different name for your mainline branch. - You cannot use a private repo for GitHub Pages, and GitHub's terms of service require you to allow other people to fork your public repositories, regardless of license. - There is no support for SSL. If you're okay with all of that, GitHub Pages is totally fine. But if you aren't, non-VPS alternatives like S3 are pretty attractive.
- 56267gs6h7u5uu 13y ago
  Re: Google--if you use a CNAME for your site on GitHub pages, will your site also show up as name.github.io in google search results?
  - itafroma 13y ago
    It shouldn't: name.github.io → example.com is a 301 redirect. However, https://github.com/name/name.github.io/blog/master/* https://github.com/name/name.github.io/blog/master/* and https://github.com/name/name.github.io/tree/master/* https://github.com/name/name.github.io/tree/master/* will show up in Google searches. Here's an example, using the atmos.org example the GitHub Pages documentation uses: https://www.google.com/search?q=Saying+how+it+was+%E2%80%9Csuper+light+and+fast+webserver+with+really+good(better+than+pound)+proxy+module.%E2%80%9D https://www.google.com/search?q=Saying+how+it+was+%E2%80%9Cs... One result for atmos.org, and then a duplicate result for https://github.com/atmos/atmos.github.io/blob/master https://github.com/atmos/atmos.github.io/blob/master. Here's a screenshot in case you see something different: http://i.imgur.com/TavoyuW.png http://i.imgur.com/TavoyuW.png The only way to prevent that from happening is to avoid using a branch named "master" in your repository.

timrivera 13y ago

That's what I immediately thought when I first read it, especially now that Github Pages are served over Fastly's CDN [1]. Then I realized that Github Pages do not support server side (301) redirects at all. Quite a big turn-off when you move an existing website over a new platform. [1] https://news.ycombinator.com/item?id=7019148 https://news.ycombinator.com/item?id=7019148, https://news.ycombinator.com/item?id=6975830 https://news.ycombinator.com/item?id=6975830

itafroma 13y ago

> And for hosting, Github pages (Jekyll rocks!) do a great job. Using GitHub pages to auto-build your Jekyll site is great if and only if you have no need to customize your Jekyll build or website environment: - You must use the versions deployed by GitHub; most of the time they're up to date, but if there's a bug fix you're relying on in any of the libraries, you're out of luck. I ran into this on my own site: RedCarpet had a Markdown parsing bug that was fixed in version 3, but the Jekyll that GitHub Pages uses depends on version 2. Jekyll loosened this dependency weeks ago, but it's not in a full release yet. - You can't use any Jekyll plugins, even the ones marked safe. You can avoid the above by building your site locally and uploading the output, there are still a few other caveats: - Like timrivera mentioned, there is no support for server-side redirects outside the baked-in ones (i.e. www to or from naked domain; name.github.io to domain). S3 has these out of the box. - You can only use one domain per GitHub Pages repository. - GitHub will allow Googlebot to index your repository's master branch. If you're used to that convention, you're out of luck: it's hardcoded into github.com's robots.txt. You need to use a different name for your mainline branch. - You cannot use a private repo for GitHub Pages, and GitHub's terms of service require you to allow other people to fork your public repositories, regardless of license. - There is no support for SSL. If you're okay with all of that, GitHub Pages is totally fine. But if you aren't, non-VPS alternatives like S3 are pretty attractive.

56267gs6h7u5uu 13y ago
Re: Google--if you use a CNAME for your site on GitHub pages, will your site also show up as name.github.io in google search results?
- itafroma 13y ago
  It shouldn't: name.github.io → example.com is a 301 redirect. However, https://github.com/name/name.github.io/blog/master/* https://github.com/name/name.github.io/blog/master/* and https://github.com/name/name.github.io/tree/master/* https://github.com/name/name.github.io/tree/master/* will show up in Google searches. Here's an example, using the atmos.org example the GitHub Pages documentation uses: https://www.google.com/search?q=Saying+how+it+was+%E2%80%9Csuper+light+and+fast+webserver+with+really+good(better+than+pound)+proxy+module.%E2%80%9D https://www.google.com/search?q=Saying+how+it+was+%E2%80%9Cs... One result for atmos.org, and then a duplicate result for https://github.com/atmos/atmos.github.io/blob/master https://github.com/atmos/atmos.github.io/blob/master. Here's a screenshot in case you see something different: http://i.imgur.com/TavoyuW.png http://i.imgur.com/TavoyuW.png The only way to prevent that from happening is to avoid using a branch named "master" in your repository.