4 ms·
One example: 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 mean
by notRobot 4y ago
One example:
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.
- Moru 4y agoJust make sure your server does not give a list of files in the directory /files/ if you do that :-)
- hnbad 4y agoIf the repo is public, people can just go to the repo and GitHub will happily give them the list of files.
- notRobot 4y agoHaha yep, made that mistake in the past!
- TurkishPoptart 4y agoHow do you do that?
- Moru 4y agoIt's a very common mistake so there is lots of help for it: You search "disable directory listing" for whatever webserver you use. I mostly use apache: https://duckduckgo.com/?q=apache+disable+directory+listing+htaccess&t=ffab&ia=web https://duckduckgo.com/?q=apache+disable+directory+listing+h...
- xigoi 4y ago> 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. Have you heard about encryption?
- notRobot 4y agoSure. I use HTTPS.
- xigoi 4y agoThat's not the point. If you want only certain people to be able to access a publicly available file, just encrypt it.
- notRobot 4y agoI could password protect it. Or I could give it a unique undiscoverable URL. It's virtually the same. 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.