5 ms·
GitHub pages [0] gives you static sites with HTTPS and a custom domain without nearly as much complexity as this if you're looking for an alternative to Netlify
by jaden 7y ago
GitHub pages [0] gives you static sites with HTTPS and a custom domain without nearly as much complexity as this if you're looking for an alternative to Netlify.
[0] https://pages.github.com/ https://pages.github.com/
- fjp 7y agoI have two sites up using GitHub Pages + Cloudflare and it's super easy and enjoyable
- jkarneges 7y agoIt even gives you a CDN. GitHub Pages is fronted by Fastly.
- ainiriand 7y agoLegitimate doubt: Fronted or frontended?
- masukomi 7y agofrontended doesn't make sense as a word. Fronted has many somewhat applicable definitions including * provide (something) with a front or facing of a particular type or material. * act as a front or cover for someone or something acting illegally or wishing to conceal something. "he fronted for them in illegal property deals" * stand face to face with; confront.
- ainiriand 7y agoThank you for the clarification.
- jobigoud 7y agoAs a non native speaker I came to the conclusion that in English it is possible to turn any noun into a verb. Not parent but "Frontended" made sense to me.
- bradknowles 7y agoI'm a native English speaker. Have been for over 50 years. Frontended sounded perfectly natural to me.
- adam1210 7y agoI tried using github pages with fastly, however it appears when a new site deployment is done, github does not invalidate the fastly cache, in addition to fastly independently caching resources on the site, which can cause broken site deployments for several minutes where it is using mixed cached resources from old and new deployments. I opened a ticket with github support, and they said it was expected behavior. It makes it partially unusable for me.
- type0 7y agoI experienced this as well, wonder if one could mitigate this with some site parameters though?
- gtirloni 7y agoI feel like Netlify has set the standard in this area now so I'm curious to learn what's different when I see these projects mentioned here.
- weego 7y agoin the case of scar you get to maintain your own AWS infrastructure. Which isn't really the goal of most people wanting a quick static site.
- nathankunicki 7y agoI had honestly never heard of Netlify. I thought GitHub Pages was the standard, with S3 static hosting a second (more involved) option. EDIT: Googling suggests Netlify offers a build, deploy, hosting pipeline all-in-one box. Which is substantially more than any of the projects mentioned here. These serve a single purpose - simple hosting of static websites.
- xondono 7y agoAlso, github pages require a public repository (or a pro account), Netlify + github doesn’t
- sharcerer 7y agothat's a bummer. I thought now that we have private free repos, websites could be hosted there. Still nice feature. I guess, the public nature definitely generates some trust and also is a good way of showing your work as Github works like a project showcase platform too.
- ztjio 7y agoYou only have to put the static content in the public repo which is no different, visibility-wise, than it is going to be anyway. So who cares? I keep my "uncompiled" site in a private repo that builds and automatically "deploys" by replacing the contents of the public repo and pushing that up. Source is private, final result is public.
- Scarbutt 7y agoGithub pages requires a paid account. https://help.github.com/en/articles/githubs-products#github-pro https://help.github.com/en/articles/githubs-products#github-...
- anonfunction 7y agoOnly for private repos, public repos can use github pages for free.
- tasuki 7y agoI've been using GitHub Pages for free on several projects for many years. Perhaps to use GitHub Pages with private repos, one has to pay?
- stock_toaster 7y agoI believe that is only for private repos.