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

Static Site Post Scheduler: Using AWS Lambda and Serverless to Schedule Blog Posts

serverless.com

Post reply on HN
Print view View original

41–48 of 48 posts

Re: Static Site Post Scheduler: Using AWS Lambda and Serverless to Schedule Blog Posts

#41

Post by rhizome »

Lord_Zero wrote: post #4
fenollp wrote: post #2

http://explainshell.com/explain?cmd=at Or use a CI cron running daily?

Yeah, they said its "serverless" but it requires an AWS lambda function. I use Jekyll for my blog but I simply commit, push, and run a script that copies the files to S3. https://www.tberra.com/aws/amazon/meta/2016/11/12/the-birth-... its not scheduled but I could easily tell linux to run that command once at whatever time I wanted.

or add a cron job to `git mv` a file from `pending` to `current` and run the commit/publish cycle.

Re: Static Site Post Scheduler: Using AWS Lambda and Serverless to Schedule Blog Posts

#43

Post by tomc1985 »

noobiemcfoob wrote: post #39
tomc1985 wrote: post #34

Earlier quoted context omitted.

Recent AWS outages come to mind... ... as for self-sufficiency, why not? You're trading freedom and independence for serfdom in Amazon's little kingdom. They'll seduce you with shit exactly like this -- stringing together pointless, useless services to achieve an end that in actuality requires 999999999% less machinery than what they sold you -- to make sure your next project is with them and all their comfy little t…

Pointing at a service with 99.99% uptime and claim the outages as a reason to go elsewhere? Host it yourself and hit that same uptime target. I'll be impressed. AWS isn't built for little static sites. It is built to host Amazon. And others likewise as big. The ability to do neat toys like this at a low cost, utilizing far more machinery than you would ever need to for such small project, is a happy byproduct. > Mean…

> Pointing at a service with 99.99% uptime and claim the outages as a reason to go elsewhere? Host it yourself and hit that same uptime target. I'll be impressed.

Well, according to pingdom I hit 99.98% uptime with the dozen-or-so cheap little DO boxes I run for my firm's infrastructure. That's playing the dual roles of sole developer and sole support on those systems. My data pipeline collects records from hundreds of deployments worldwide, through all manner of diverse corporate IT environments. It really isn't that hard.

I'll agree with your points on frictional unemployment when the thing displacing them represents actual forward progress. AWS is a land grab, not progress.

Re: Static Site Post Scheduler: Using AWS Lambda and Serverless to Schedule Blog Posts

#45

Post by rathboma »

With Jekyll you can just future-date your blog posts then trigger a republish on a daily cron. By default future-dated posts won't show up. So a daily build will publish them on the right day.

If you host using Netlify you can create a build hook to just curl. You could even use Cronitor for a free cron.

Re: Static Site Post Scheduler: Using AWS Lambda and Serverless to Schedule Blog Posts

#46

Post by tomc1985 »

davidwells wrote: post #28
tomc1985 wrote: post #24

Earlier quoted context omitted.

Does this not seem excessive? Doesn't anyone care about simplicity, or elegance, or -- at minimum -- not relying on others?

Good point. I care greatly about these things. This project greatly simplifies how we publish content in an elegant out of sight out of mind way. Before, if someone was out of town, we would need to rely on others to push the merge button on posts for us. Now, the robots do it for us!

While I don't know your situation your use case is understandable. It's just hard to watch such big tools serving up simple HTML with what could be a shell script or two running in cron.

Re: Static Site Post Scheduler: Using AWS Lambda and Serverless to Schedule Blog Posts

#47

Post by geekjock »

foxhop wrote: post #8

This solution is sort of weird to me. To me, the allure of a static site or a static blog is to simplify the stack; To bring it back to the basics. Static HTML served by a good ole-fashion web server. Adding the cognitive burden of "serverless" and/or lambda just to schedule seems to complicate something that isn't very complicated. Its almost like an invented problem. That said, long live this static site generator…

Founder of https://buttercms.com here – we should talk!

Re: Static Site Post Scheduler: Using AWS Lambda and Serverless to Schedule Blog Posts

#48

Post by nickjj »

rathboma wrote: post #45

With Jekyll you can just future-date your blog posts then trigger a republish on a daily cron. By default future-dated posts won't show up. So a daily build will publish them on the right day. If you host using Netlify you can create a build hook to just curl. You could even use Cronitor for a free cron.

This is what I do too. It works well.

Although in my case, I host my Jekyll based site on my own server and just run a daily build via local cron.

The workflow to post anything (present or scheduled) is nothing more than a single git push to get the new content on the server.

It's as simple as can be. #serversforlife

Post reply on HN