Good article but confused by:
"Unless you pay, GitHub Pages requires your repository to be public."
How is that a problem with a static website?
"Unless you pay, GitHub Pages requires your repository to be public."
How is that a problem with a static website?
All files/pages will be publicly discoverable. I regularly chuck stuff on a webserver to share files (like /files/dat-283992.txt) that's only meant to be accessed by people I share the URL with, but that's not possible when the repo is public.
Additionally, your Jekyll config files will also be public, which I guess some people might not want, for whatever reason.
https://duckduckgo.com/?q=apache+disable+directory+listing+h...
Have you heard about encryption?
It's no different than sharing a link to a file in your Google Drive accessible only to people with the URL.
Encryption doesn't play the role you seem to think it plays here.
Yes, aka encrypt it.
> Or I could give it a unique undiscoverable URL.
…which is not possible if the repository is public.