3 ms·
I know the author said automation wasn't what they wanted, but gods below this problem begging to be automated away. 1) Only compile newly updated items. 2) g
by falcolas 12y ago
I know the author said automation wasn't what they wanted, but gods below this problem begging to be automated away.
1) Only compile newly updated items.
2) git commit -am 'new post'
3) git push origin master
The first step needs to be built out in the tool itself, but the rest is a simple bash script, really. It's not even something that needs to be monitored. If you did want to monitor it, it's a few simple `curl` commands away from pushing to prowl or NMA. No need to sit at your computer waiting for it to finish.
Seems like a good weekend project - build a set of tools around Jekyll (and/or any number of other static site generation tools), and let the laurels rain down.
- krat0sprakhar 12y agoCan't agree with this more. All you need is a simple rakefile[0] that does it for you. I have something like this for myself - prakhar1989.github.com git/master* $ rake rake default # List tasks rake draft # Create a new draft in ./_drafts rake post # Create a new post in ./_posts rake preview # Live Preview (use mode=drafts for drafts) rake publish # Push to github [0] - https://github.com/prakhar1989/prakhar1989.github.com/blob/master/Rakefile https://github.com/prakhar1989/prakhar1989.github.com/blob/m...
- ojilles 12y agoI have the same, with one addition (that would be running at the end of your 'publish' step): a 47-line bash script that will spider the whole site to find any internal 404 links. https://github.com/ojilles/jilles.net/blob/master/_bin/wget-test.sh https://github.com/ojilles/jilles.net/blob/master/_bin/wget-... (Poorly implemented but works for me)