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

1–10 of 48 posts

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

#4

Post by Lord_Zero »

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.

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

#5

Post by g_delgado14 »

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.

AWS lambda functions __are__ serverless. There's no notion of uptime, provisioning or managing servers when using lambda.

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

#7

Post by davidwells »

crisopolis wrote: post #6

Since serverless uses AWS primarily. I'm assuming if I put all my eggs in the serverless basket and Amazon has some amazing outage. I'm screwed? To which I don't understand the appeal of serverless besides having no servers lol.

Hello there! The serverless framework supports a number of different FAAS (function as a service) providers like IBM openwhisk, AWS lambda, & Azure functions from microsoft. See https://serverless.com/framework/docs/providers/ for more info.

So it's up to you where your code runs =)

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

#8

Post by foxhop »

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

I'm betting this movement will continue to grow which is why I'm bootstrapping https://www.remarkbox.com (comments-as-a-service)

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

#9

Post by cocktailpeanuts »

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…

I use jekyll NOT because it's simple (Actually it's 100 times more complex to use than a simple wordpress or medium) but because:

1. I can keep track changes with git 2. I can host them on Github pages for FREE 3. I own the content 4. More flexible

In fact I've been really annoyed with all the boilerplate code and extensions I need to deal with in order to have a "usable" workflow set up, I almost thought about moving back to free blog services like medium, tumblr, wordpress, etc. but the only reasons I can't are the ones I mentioned above.

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

#10

Post by davidwells »

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…

Thanks for the comment foxhop! We try to keep things as simple as possible where we can.

This project came out of the need from our content team needing to publish content late at night and when people are out of office =)

Check out the code https://github.com/serverless/post-scheduler/blob/master/han... this serverless service is just 2 functions that get deployed. It's a set it and forget it service =)

Post reply on HN