What are webhooks limitations in terms of number of posts or amount of content? Is this dictated by the cost of storage in Google Cloud Engine and possibly Elastic Search? Does webhook impose its own limitations that would require one to self host or do the costs simply go up?
nvm, found this post from Dave Snider:
"There's no problem with a large number of images. There's a problem with a large number of pages. As the number of pages increases, your compile time will also increase. This is true of any static system, and Webhook is not alone here. It becomes noticeable once you start building over a thousand pages and budd's breakdown reads true in that regard.
As for serving images, we tier it based on bandwidth usage (as seen on our homepage):
$9 hosting covers 25GB monthly bandwidth, with pay as you go $0.15 / per GB afterwards. That's essentially 250,000 pageviews a month.
Currently, no one hits those needs at the moment. Also, there's nothing stopping you from using a CDN for your image use and webhook for the actual site CMS. There's also nothing stopping you from taking your .build directory and putting the entire site on a CDN too if you want. Some people are paranoid about hosting and go to that level, or self-host themselves.
Also, and this should be obvious, but you want the images uploaded / referenced in the CMS itself, not in the static directory. We deploy your entire local site, and if there's a large amount of files in there, you'd be uploading it every time.
From a practicality standpoint I'd say if you plan on publishing hundreds of GBs of images you likely are going to want to look into something more tailored to your needs. At that point you're building a mini-flickr."