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

Poll: Where do you host your static website?

news.ycombinator.com

Post reply on HN
Print view View original

41–50 of 58 posts

Re: Poll: Where do you host your static website?

#41

Post by philip1209 »

tikhonj wrote: post #31

I use a static site generator (Hakyll) and deploy directly to S3. It's a pretty awesome system. I also used to use CloudFront as a CDN. I gave up because invalidating the cache was a bit tedious. I should start using it again for the assets that usually don't change like fonts. It's really not difficult; it was just inconvenient because I was using it for things like text that I updated constantly.

I use Jekyll and deploy to S3 too - combining it with Cloudflare provides an easier partial-CDN and some tools like 301 redirects that S3 doesn't provide out of the box:

http://www.brouhaha.io/practical-jekyll/

Re: Poll: Where do you host your static website?

#42

Post by orangethirty »

fakeer wrote: post #37
orangethirty wrote: post #6

Webfaction++

I struggled to put up a static generator over there I failed, I tried everything I could. Of course they were helpful but asking them to enable this, enable that every time is plain painful. I also tried to setup ownCloud and didn't succed again. Finally I moved to vps and I set them up there with some difficulty and then I moved my static files back to Dropbox and left OwnCloud. It was too much trouble. WebFaction o…

When was this?

Re: Poll: Where do you host your static website?

#48

Post by Smudge »

tikhonj wrote: post #31

I use a static site generator (Hakyll) and deploy directly to S3. It's a pretty awesome system. I also used to use CloudFront as a CDN. I gave up because invalidating the cache was a bit tedious. I should start using it again for the assets that usually don't change like fonts. It's really not difficult; it was just inconvenient because I was using it for things like text that I updated constantly.

I've considered hosting my assets on a separate domain (e.g. assets.mydomain.com) because, in theory, browsers will better be able to parallelize the downloads. It sounds like this same approach would make your CloudFront setup a bit easier to manage.
Post reply on HN