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.
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/...). 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.
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.
It's good security because APIs are just another way to gain access to your stuff, and an attacker controlling your DNS has _incredible_ access to ruin your life (steal email, impersonate you... the works).
It's bad though because increasingly we're automating certificates and other stuff through means of using DNS as proof (i.e. set a magic TXT record and lets encrypt will grant you a wildcard SSL cert for free) and many scripts need a DNS provider with good API.
So long way of saying for basic stuff where it's just you going into a dashboard and clicking around to change settings--Namecheap is great. Their DNS comes free with purchase of a domain for a couple bucks, you really can't beat that price.
If you need programmatic API access step up to someone who is running DNS as a core part of their business IMHO--Amazon Route 53, Cloudflare, etc. The bigger the better as they'll have more security resources, support good security practices like 2FA, hardware auth devices, etc. and just generally have more care taken with access to DNS. You'll pay more but you'll get more in the long run.
The default setup for GH Pages is not great. Jekyll is very dated. But if you use GH Actions, you can build yourself a pretty great setup. My site is open source at https://github.com/jacobp100/jacob-does-code - there's also a blog post about how the build system works.
As someone who does a lot of browsing with unpopular web browsers, Cloudflare is basically a way to ensure that it is a coin toss as to whether or not I will see your site; it is not the worst CDN/DoS protection racket service out there though. I would like to see how much legitimate traffic Cloudflare or the others block, and how much website operators are spending on that "service."
If I don't care about anti-ddos, I just set the Firewall security to Low, and create a Firewall rule to allow everything from 0.0.0.0/0, simple as that.
Or are there reasonable software or hardware options to protect one’s own servers directly without relying on a third party service?
Third party free hosting excels at the ability to do a start to finish page in inside an hour. I want to spend 55 minutes of that hour writing the text, not fiddling with oddities of how to make GitHub actions show me the parse errors of my markdown...
That is not the case with netlify.com which boasts a myriad of features, is equally as fast, production-ready, and competitively priced.
With pages.dev, I believe, you pay per every domain you host, whilst with netlify.com, there's no cap on number of domains per account, though they do charge for bandwidth (unlike pages.dev).
Workers Sites [1] is a viable alternative and I quite prefer it over pages.dev.
[0] https://developers.cloudflare.com/pages/platform/limits
[1] https://developers.cloudflare.com/workers/platform/sites
nope, we do unlimited sites on pages! here's the free plan [1]:
> 1 build at a time
> 500 builds per month
> Unlimited sites
> Unlimited requests
> Unlimited bandwidth
you can upgrade to the pro ($20/mo) or business ($200/mo) plans for more concurrent builds and builds per month. still not priced per domain or site!
> ...still not priced per domain or site!
It was my understanding that I had to upgrade each domain to "pro" with $20/month (say, if I wanted pro features like web-analytics on each). Is that not the case?
On netlify.com, "pro" is $19/month per account (not per domain).
* Three reasons. 1) The identity widget has people setting it up in such a way that tokens aren't refreshed and logins last only an hour. https://github.com/netlify/netlify-identity-widget/issues/11... 2) Netlify Identity keeps bumping me out despite having gone out of my way to get it configured properly. I don't know why but the issue has lasted for weeks. 3) In development mode, the token can't be verified without making a request to Netlify Functions, and the suggested path (in Redwood.js at least) is to just parse the JWT without verifying it.
I meant in a way that pages.dev is in "open beta" and netlify.com don't market themselves as such.
Besides, in my personal experience, I never hit any issue with netlify that didn't have a solution.
https://developers.cloudflare.com/pages/migrations/migrating...
we don't have any plans to get rid of workers sites! but we do think that for most people deploying static sites, pages is a better fit than workers sites.
when we do talk about the future of pages versus workers sites, we're generally talking about making it easier to deploy serverless functions /with/ your pages sites - providing better tooling and DX around that is a super high priority for us.
the interplay between workers serverless functions and static asset serving via workers sites is still a really strong use case (and IMO a thing that workers is uniquely capable of doing) that we don't have any plans to shelf. again, i wrote the docs here so this is on me if it came across as "we're getting rid of workers sites" - i'll take a shot at improving these docs and helping clarify that next week!
What do you mean by that? I've been (and still am) hosting quite a few pages with their service using custom domains and have never been charged for that.
Saying that because I tried it out again a few weeks ago for a friend's website (https://neasair.org), and nope... it doesn't provide AAAA DNS records (IPv6), just A (IPv4).
So, had to put the website on some other infrastructure already hanging around, that does do AAAA records.
Gitlab pages has an option to look at the /build folder for web pages to serve up. So as long as that folder is in the .gitignore, my Gitlab ci just runs `hugo` to build the site which then gets served up.
"With GitLab Pages, you can publish static websites directly from a repository in GitLab. Use for any personal or business website."
"GitHub Pages is not intended for or allowed to be used as a free web hosting service to run your online business, e-commerce site, or any other website that is primarily directed at either facilitating commercial transactions or providing commercial software as a service (SaaS)."
Now one could read that as "don't build a SaaS on top of GitHub Pages", but you could also read that as "don't have business websites on GitHub Pages".
That is Netlify and Cloudflare Pages' defining feature, and GitHub has had that for a few years now.
You can configure github projects to source from a different branch (including your main/master branch if you check in build artifacts directly)
Granted, my blog is an insignifcant site with a tiny readership and I rarely update it, so if you need something more heavy duty than I have no idea if GH pages is up to the task.
You don't need that anymore. You can run Github Pages out of a branch like /docs, which makes life much simpler. That's how I run most of my sites.
- I've got several sites on gh-pages with custom domains and pay exactly $0
- I don't use Jekyll, I literally just `git push` a static repo
For everything else it expects your SPA to handle it.
Github pages is fine, but the extra gh-pages branch is kind of annoying. It's fairly clear (for obvious reasons) that they mainly think about Jekyll users, though I had a Hugo blog there for a while.
Netlify sounds great, but in practice I ran into an annoying issue that I couldn't resolve where I had to rerun every automatic build. This probably isn't really their fault but the forums didn't work.
Cloudflare Pages kind of just worked out of the box, and since I was already using it for my DNS, changing where the domain pointed took a few seconds.
I'd suspect, if you corrected for how many issues were particular to me, I'd say Cloudflare Pages ~ Netlify > Github Pages. I'm kind of surprised the latter charges you for custom domains; I do have to say there's more documentation for Github than any of the others.