Automate GitHub Pages with IFTTT, Glitch and Jekyll
webrender.net
Automate GitHub Pages with IFTTT, Glitch and Jekyll
1–10 of 30 posts
Re: Automate GitHub Pages with IFTTT, Glitch and Jekyll
#2This is exactly what I need for one of my projects - thanks for posting!
Re: Automate GitHub Pages with IFTTT, Glitch and Jekyll
#3I'm a big fan of IFTTT. This is interesting.
Re: Automate GitHub Pages with IFTTT, Glitch and Jekyll
#4Can Glitch run arbitrary Node.js like Webtask?
Re: Automate GitHub Pages with IFTTT, Glitch and Jekyll
#5Can Glitch run arbitrary Node.js like Webtask?
Yes
Re: Automate GitHub Pages with IFTTT, Glitch and Jekyll
#6How does Glitch compare to Heroku or ZEIT Now?
Re: Automate GitHub Pages with IFTTT, Glitch and Jekyll
#7Wouldn't it be simpler to host a lightweight dynamic website?
Automatic commits to a git repo of a static website to make it reflect dynamic data reminds me of https://news.ycombinator.com/item?id=15272144
Re: Automate GitHub Pages with IFTTT, Glitch and Jekyll
#8Wouldn't it be easier to just merge a PR branch (containing the post) in Github or Bitbucket??
Also: less parts involved
Re: Automate GitHub Pages with IFTTT, Glitch and Jekyll
#9I'm fascinated how far we can take SaaS solutions to build something you would usually deploy on PaaS before (i.e. a CMS).
While a slightly unrelated question, I was wondering: is there a PaaS platform which really replaces AWS ec2 instance by flexibility/capabilities? EC2 has great ecosystem (RDS+Elastic Cache+S3) and great flexibility of just setting up some extras on the side (App specific cron jobs+Letsencrypt cron jobs). Is there an offering which could really provide all that without going onto IaaS (which is what ec2 is) level?
Re: Automate GitHub Pages with IFTTT, Glitch and Jekyll
#10How does Glitch compare to Heroku or ZEIT Now?
Well, for, starters, Glitch is free for unlimited usage :)
Glitch is geared towards people collaboratively working on Node apps (it doesn't support anything else, unlike the other options).
However, it's much easier to get started, with an in-browser code editor, console, and starter projects.
I've been using Glitch to play around with ideas mostly and then I will build locally and deploy to something like Heroku. One other downside of Glitch is that source code is viewable by anyone, which means you probably don't want to launch a side project there.
Note: don't work for Glitch, Heroku, or anyone else mentioned