Live data from Hacker News

Automate GitHub Pages with IFTTT, Glitch and Jekyll

webrender.net

11–20 of 30 posts

Re: Automate GitHub Pages with IFTTT, Glitch and Jekyll

#11
post #9

I'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 cr…

Azure has been something I've considered for this exact purpose. The PaaS and ARM Templates abstract away IaaS and provides both configuration and secret management.

It should be possible for someone to deploy a Mastodon or Matrix instance via Azure PaaS with no IaaS management necessary. With Kudu's Git triggers, automatic updates might even be possible!

It's no small feat though. It also would require a great deal of ARM JSON which is painful at times.

Re: Automate GitHub Pages with IFTTT, Glitch and Jekyll

#12
post #6

How 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. On…

You can set your Glitch project to private to hide the source code under advanced options from the top-left project info menu.

Re: Automate GitHub Pages with IFTTT, Glitch and Jekyll

#13
post #7

Wouldn'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

There's a couple different reasons I ended up going with this solution for my site:

1) Most of the time, integrating social networks into your site means either a) using widgets that are hard to work into the main site flow or b) having a backend to pull and integrate social media posts for you. This solution essentially provides B without needing to maintain a backend.

2) When planning my site refactor, Github Pages appealed to me because of its speed and simplicity. This lets me preserve the site automation that would previously have required a CMS, and because the site is static and hosted by Github, I don't need to worry about bandwidth or usage limits.

Re: Automate GitHub Pages with IFTTT, Glitch and Jekyll

#14

I'm a big fan of IFTTT. This is interesting.

Upvoted, because there's nothing wrong with this sort of comment, and this and the posts above represent two sides of the same coin--one wants to support, the other wants to tear down, but is shielded behind a veneer of "helpfulness" or "constructive criticism," when in fact it is not.

Complainers complain, and like attracts like. If people want to assert that supportive comments don't "contribute," then knee-jerk downvotes for their own sake are equally unhelpful.

Re: Automate GitHub Pages with IFTTT, Glitch and Jekyll

#15

I'm a big fan of IFTTT. This is interesting.

Upvoted, because there's nothing wrong with this sort of comment, and this and the posts above represent two sides of the same coin--one wants to support, the other wants to tear down, but is shielded behind a veneer of "helpfulness" or "constructive criticism," when in fact it is not. Complainers complain, and like attracts like. If people want to assert that supportive comments don't "contribute," then knee-jerk do…

All it takes is a "because". I'm a big fan of X because it has provided Y benefit. This helps others decide when such a software/product is useful.

Otherwise the comment is an unsubstantiated "me too", for which an upvote already exists. Such low quality comments are a... relatively new trend on HN.

Not to mention complaints about downvotes are directly against HN policy.

Re: Automate GitHub Pages with IFTTT, Glitch and Jekyll

#16
I have been using WordPress for my personal blog and such task is trivial in WordPress with built-in sharing feature. What's more you can have control over the source code when you host it on your own VPS. The free WordPress hosting by wordpress.com has the same functionality built-in.

What are some of the advantages of using this workflow involving multiple services/tools? I feel that this is too many dependencies to accompany a simple task.

Re: Automate GitHub Pages with IFTTT, Glitch and Jekyll

#18

I have been using WordPress for my personal blog and such task is trivial in WordPress with built-in sharing feature. What's more you can have control over the source code when you host it on your own VPS. The free WordPress hosting by wordpress.com has the same functionality built-in. What are some of the advantages of using this workflow involving multiple services/tools? I feel that this is too many dependencies t…

This seems like too easy a question, but

- WordPress is dynamic, not static, which contributes to:

- WordPress takes more resources to run, and

- WordPress regularly has security holes

- WordPress is therefore not simple because it requires maintenance

- WordPress relies on countless server- and client-side dependencies, which contributes to the maintenance and server requirements

Re: Automate GitHub Pages with IFTTT, Glitch and Jekyll

#20
post #7

Wouldn'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

I'm doing the same thing for a few of my personal tools, and once you get over the instinctive revulsion it's a remarkably nice data flow. For example, I maintain state for an IRC D&D game using a bot that publishes to a github static page after every character-sheet edit. The big win is that I don't have to worry about hosting or availability - the bot only has to be up when the game is in session, the rest of the time, github provides for anyone that wants to look at their character sheet or anything. I do the same thing to maintain an el cheapo bash.org slash bucket [1] for a discord community I'm part of; again, a discord bot is significantly easier to keep alive than a website.

[1] https://github.com/zigdon/xkcd-Bucket

Post reply on HN