No Server Required - Jekyll & Amazon S3
allthingsdistributed.com
No Server Required - Jekyll & Amazon S3
1–10 of 39 posts
Re: No Server Required - Jekyll & Amazon S3
#2Re: No Server Required - Jekyll & Amazon S3
#3Except for the servers at Disqus which are running the comment system. And the servers serving up the static HTML pages.
Re: No Server Required - Jekyll & Amazon S3
#4Re: No Server Required - Jekyll & Amazon S3
#5Except for the servers at Disqus which are running the comment system. And the servers serving up the static HTML pages.
Aha! That's how he did it. I couldn't figure out how commenting worked. He does have a comment count link at the top of the page. Is that fragment from Disqus also?
Re: No Server Required - Jekyll & Amazon S3
#6Re: No Server Required - Jekyll & Amazon S3
#7Coming from the CTO of Amazon...
Re: No Server Required - Jekyll & Amazon S3
#8This is a pretty over-used subject for blog submissions here on HN, see previous ones at https://encrypted.google.com/search?q=site%3Anews.ycombinato...
Re: No Server Required - Jekyll & Amazon S3
#9Re: No Server Required - Jekyll & Amazon S3
#10I remember running this type of setup back in 2003 with text files and Blosxom. What's old is new again?
But yes, I guess there is some movement back in time. I'd say the two main reasons are a return to more minimal blogging (i.e. something like tumblr as opposed to blogrolls, widgets, plugins etc.), and the fact that you can do some dynamic stuff in the client now via JavaScript (e.g. comments with Disqus).