4 ms·
Basically everything you wrote about GitHub Pages is wrong. GitHub Pages is static hosting. If you don’t need Jekyll, don’t use it. There’s nothing special abo
by thitcanh 6y ago
Basically everything you wrote about GitHub Pages is wrong.
GitHub Pages is static hosting. If you don’t need Jekyll, don’t use it. There’s nothing special about it.
GitHub Pages does NOT charge for custom domains.
You can configure any branch for GitHub Pages, or even just the /docs folder on the main branch.
- qbasic_forever 6y agoJust as a clarification, much of what you mention has only changed in the last year or so. For a very long time gh-pages branch and Jekyll were assumed (you couldn't even use plugins with Jekyll). Custom domains weren't free. SSL wasn't free. Github is doing great stuff but it has taken time to evolve into the all free all you can eat buffet you see today.
- hellojason 6y agoI have to agree with parent. I've had a custom domain without Jekyll on GitHub pages for well over 5 years now, and it's been free the entire time.
- heyoni 6y agoSame here. Not sure where they’re getting that from. Possibly region specific?
- singhrac 6y agoI replied upthread, but I made a mistake reading https://docs.github.com/en/github/working-with-github-pages/about-custom-domains-and-github-pages https://docs.github.com/en/github/working-with-github-pages/... when revisiting what I remembered, and I was just looking at it from the perspective of private repos. My bad!
- hellojason 6y agoOh right, good point. The repo had to be public until very recently.
- villgax 6y agoGet your facts straight, they have had custom domains for a looong time & there was absolutely no need for Jekyll either at any point to host a page, it just happened to be one the most documented/blogged about way to use GitHub pages with automatic builds instead of having static content.
- stevage 6y agoMuch more than a year, maybe 2-3 years.
- singhrac 6y agoI think we've both said correct things, but I think you've missed my meaning: yes, I understand that Github Pages is static hosting, I was point out that by default the build system uses Jekyll. This is nonobvious. This is in the docs: "GitHub Pages will use Jekyll to build your site by default. If you want to use a static site generator other than Jekyll, disable the Jekyll build process by creating an empty file called .nojekyll in the root of your publishing source, then follow your static site generator's instructions to build your site locally." (https://docs.github.com/en/github/working-with-github-pages/about-github-pages#static-site-generators https://docs.github.com/en/github/working-with-github-pages/...). Netlify and CF will both run some other static site generators (e.g. Hugo in my case) for you, while Github Pages will run Jekyll (or you can build locally). And yes, custom domains are free for public repos. I made a mistake reading the page about custom domains, which mentioned that private repos need a Github Pro account. You're also right about configuring any branch.
- stevage 6y agoI don't use Jekyll and I have never set up a .nojekyll file. I don't know what that is meant to do, but you can deploy whatever you want and it will work just fine. Maybe you need that file on the rare offchance that you're deploying a site that contains something that looks like a Jekyll config, but you don't want it to be built that way.
- tomerv 6y agoYes, that's exactly the issue. I don't remember the exact file name, maybe it was a directory named "static". The behavior was not as expected, and only a Google search helped me figure out why files were disappearing.