Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitHub Pages – Usage Limits

help.github.com

Post reply on HN
Print view View original

61–70 of 101 posts

Re: GitHub Pages – Usage Limits

#61

Post by saddestcatever »

benbalter wrote: post #54

I am the Product Manager for GitHub Pages. As has been mentioned multiple times here, the usage limits were not in response to a specific external event. The limits have been an internal policy (in one form or another) for as long as I've been involved (nearly 4 years now), and we chose to publicize them in a series of updates beginning early this summer. This is a classic case of "this is why we can't have nice thin…

Thank you. Seriously. GitHub Pages is a great service. It's saved me in a whole number of smaller projects. The Usage Limits are surprisingly liberal considering it's a complimentary service! So, thank you and your team!

Re: GitHub Pages – Usage Limits

#62

Post by jda0 »

ploggingdev wrote: post #57
benbalter wrote: post #54

I am the Product Manager for GitHub Pages. As has been mentioned multiple times here, the usage limits were not in response to a specific external event. The limits have been an internal policy (in one form or another) for as long as I've been involved (nearly 4 years now), and we chose to publicize them in a series of updates beginning early this summer. This is a classic case of "this is why we can't have nice thin…

Do the "requests" mean page views or http requests? A single page view almost always has multiple http requests. Github really needs to add https support for custom domains. It's 2016, https should be the default. [Reposting my comment]

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-wit...

Re: GitHub Pages – Usage Limits

#63

Post by jda0 »

Ajedi32 wrote: post #49
strcat wrote: post #39

Earlier quoted context omitted.

"HTTPS is not supported for GitHub Pages using custom domains." - this is what they mean, they weren't specific.

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.

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-wit...

Re: GitHub Pages – Usage Limits

#65

Post by ploggingdev »

jda0 wrote: post #62
ploggingdev wrote: post #57

Earlier quoted context omitted.

Do the "requests" mean page views or http requests? A single page view almost always has multiple http requests. Github really needs to add https support for custom domains. It's 2016, https should be the default. [Reposting my comment]

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-wit...

The route from the user's browser to Cloudflare is encrypted (https), but the route between Cloudflare's servers and github pages is only http as Github does not support https for custom domains.

User Cloudflare Github pages

Re: GitHub Pages – Usage Limits

#66

Post by JD557 »

benbalter wrote: post #54

I am the Product Manager for GitHub Pages. As has been mentioned multiple times here, the usage limits were not in response to a specific external event. The limits have been an internal policy (in one form or another) for as long as I've been involved (nearly 4 years now), and we chose to publicize them in a series of updates beginning early this summer. This is a classic case of "this is why we can't have nice thin…

> Additionally, GitHub Pages sites must refrain from:

> Pornographic content

How strict is this rule?

There has been some interesting open source AI projects related to NSFW images (eg. Yahoo_NSFW, Open_NSFW, MilesDeep). What is GitHub's policy regarding this projects? Could a GitHub page present results? What about a link to download a training dataset?

I also just noticed that Open_NSFW's web page is hosted on GitLab (https://open_nsfw.gitlab.io/). Would a page like this (which might be considered pornographic, depending on your interpretation) be allowed on GitHub pages?

Re: GitHub Pages – Usage Limits

#67

Post by kyledrake »

Touche wrote: post #43
kyledrake wrote: post #24

##### 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 ye…

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.

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.

Re: GitHub Pages – Usage Limits

#68

Post by cbr »

blobman wrote: post #3

If you're getting over the bandwidth limit of 100GB or 100,000 requests per month, you could definitely afford to host your site elsewhere...

My blog serves ~500k requests per month, mostly to bots. My pages generally have few external resources; with a typical CMS site this would be more like 5M requests.

(This is with ~15k pageviews-not-from-bots per month.)

Re: GitHub Pages – Usage Limits

#69

Post by brianllamar »

JamieF1 wrote: post #10

Is this not a chance for github to make some money? I'm about to launch a site on github pages (simple html site, no backend) and there's a tiny chance of it going viral. If it were to reach the 100k limit for requests I'd be more than happy paying github to keep it hosted there. I already have hosting with the likes of hostgator but they probably couldn't even handle 100k like github would.

To add to the list of alternatives, try netlify it has a free tier with no build limits and provides a pretty liberal and free open-source plan that has more feature than GitHub pages. https://netlify.com/open-source. Just throwing out there as well.

you can also connect your github repo to have a atomic deploys, which is more than you get from gh pages. https://www.netlify.com/blog/2016/08/11/from-unstable-to-rel...

Re: GitHub Pages – Usage Limits

#70

Post by blackguardx »

newscracker wrote: post #42
JamieF1 wrote: post #10

Is this not a chance for github to make some money? I'm about to launch a site on github pages (simple html site, no backend) and there's a tiny chance of it going viral. If it were to reach the 100k limit for requests I'd be more than happy paying github to keep it hosted there. I already have hosting with the likes of hostgator but they probably couldn't even handle 100k like github would.

For simple static pages (with no backend), I would highly recommend putting them on Nearly Free Speech (NFSN) [1] and using the free tier of CloudFlare in front of it. NFSN charges only for what you use, unlike hosts like hostgator and others that have a monthly payment of a few dollars, at the minimum. Excluding domain costs, it will cost you just pennies a year or a few dollars a year. You can also opt for cheaper…

I used to host some stuff on nearlyfreespeech. I liked the idea in principle, but keeping my account topped up and them charging me extra fees just to pay them became annoying. I switched to Amazon S3 and couldn't be happier. It was harder to setup but worth it.
Post reply on HN