3 ms·

##### EDIT: The title for this link started as "GitHub Pages sets usage limits", but was changed to "What is GitHub Pages?" by an HN moderator, putting this pos

##### EDIT: The title for this link started as "GitHub Pages sets usage limits", but was changed to "What is GitHub Pages?" by an HN moderator, putting this post (and most of the discussion going on in here) completely out of context. I don't agree with this decision. Most HN readers know what Github Pages is - it's the new usage caps that are the news here. Those caps are new - I've been tracking Github Pages for years, and the only cap they previously set was the 1GB repo size (total changes ever) limit, and occasional heresay from people that used to work on it: https://www.quora.com/What-are-bandwidth-and-traffic-limits-for-GitHub-pages/answer/Zach-Holman https://www.quora.com/What-are-bandwidth-and-traffic-limits-... https://neocities.org https://neocities.org free plan, for comparison: Storage: 100MB (1GB by end of January). Bandwidth: 50GB (never been enforced, many sites are over and it's fine). SSL: Yes (forced SSL starting Jan 1st). Change limit: one per minute, never enforced. Number of hits: No set limit, would be in the millions if I did. Number of changes: No set limit, not enforced, probably never will be. But our usage limits aren't going down - they're constantly going up as we upgrade and improve our infrastructure. In fact, due to some upgrades to our anycast CDN I'm going to raise the BW limit to 200GB right now. Merry Christmas.

nrjdhsbsid 10y ago
GitHub pages don't support HTTPS so they're increasingly a no-go for me :(. So many endpoints are HTTPS only now that the mixed content warnings are too much hassle to deal with
- antoinealb 10y ago
  In fact, they support HTTPS: https://help.github.com/articles/securing-your-github-pages-site-with-https/ https://help.github.com/articles/securing-your-github-pages-...
  - strcat 10y ago
    "HTTPS is not supported for GitHub Pages using custom domains." - this is what they mean, they weren't specific.
    - Ajedi32 10y ago
      A lot of people work around that by doing GitHub Pages + Cloudflare. It's free, and it gets you all the additional performance benefits that Cloudflare provides. Would probably also prevent you from running into any of these bandwidth limits.
      - jda0 10y ago
        This is what I do and it's great. CloudFlare supports HTTPS for GitHub Pages, would definitely recommend it as although Namecheap is pretty good CloudFlare make everything DNS, CDN and security related soo easy for $0. (I'm not affiliated with them in any way :P ) https://blog.cloudflare.com/secure-and-fast-github-pages-with-cloudflare/ https://blog.cloudflare.com/secure-and-fast-github-pages-wit...
      - tedmiston 10y ago
        The Cloudflare setup is only secure from user to Cloudflare, not from Cloudflare to GitHub.
Touche 10y ago
Does Neocities support anything like webhooks, so people can do normal workflow of pushing to GitHub and having it be auto-deployed. Or even pushing to a Neocities remote would be fine too. I currently use a Raspberry Pi server that uses webhooks and it's very nice.
- nilved 10y ago
  It doesn't have webhooks, but it has a full API. You could use CircleCI or another build tool to publish your site when you push to GitHub. This way you also get more control over the build process and can use tools other than Jekyll. https://neocities.org/api https://neocities.org/api You could also create a webhook using their API and AWS API Gateway + Lambda.
- kyledrake 10y ago
  There's an API right now. Github webhooks are coming, as is git push support. They were sidelined to facilitate the infrastructure upgrades so we could provide more bandwidth and storage. We'll get back to them.

nrjdhsbsid 10y ago

GitHub pages don't support HTTPS so they're increasingly a no-go for me :(. So many endpoints are HTTPS only now that the mixed content warnings are too much hassle to deal with

antoinealb 10y ago
In fact, they support HTTPS: https://help.github.com/articles/securing-your-github-pages-site-with-https/ https://help.github.com/articles/securing-your-github-pages-...
- strcat 10y ago
  "HTTPS is not supported for GitHub Pages using custom domains." - this is what they mean, they weren't specific.
  - Ajedi32 10y ago
    A lot of people work around that by doing GitHub Pages + Cloudflare. It's free, and it gets you all the additional performance benefits that Cloudflare provides. Would probably also prevent you from running into any of these bandwidth limits.
    - jda0 10y ago
      This is what I do and it's great. CloudFlare supports HTTPS for GitHub Pages, would definitely recommend it as although Namecheap is pretty good CloudFlare make everything DNS, CDN and security related soo easy for $0. (I'm not affiliated with them in any way :P ) https://blog.cloudflare.com/secure-and-fast-github-pages-with-cloudflare/ https://blog.cloudflare.com/secure-and-fast-github-pages-wit...
    - tedmiston 10y ago
      The Cloudflare setup is only secure from user to Cloudflare, not from Cloudflare to GitHub.

Touche 10y ago

Does Neocities support anything like webhooks, so people can do normal workflow of pushing to GitHub and having it be auto-deployed. Or even pushing to a Neocities remote would be fine too. I currently use a Raspberry Pi server that uses webhooks and it's very nice.

nilved 10y ago
It doesn't have webhooks, but it has a full API. You could use CircleCI or another build tool to publish your site when you push to GitHub. This way you also get more control over the build process and can use tools other than Jekyll. https://neocities.org/api https://neocities.org/api You could also create a webhook using their API and AWS API Gateway + Lambda.
kyledrake 10y ago
There's an API right now. Github webhooks are coming, as is git push support. They were sidelined to facilitate the infrastructure upgrades so we could provide more bandwidth and storage. We'll get back to them.