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

Benefits of a Git-backed Blog

davidsweetman.com

Post reply on HN
Print view View original

11–17 of 17 posts

Re: Benefits of a Git-backed Blog

#11

Post by VMG »

pilif wrote: post #4

There is a simple rule of thumb about unix tools: when you are in need of a -f or --force parameter, most likely something is wrong and you should rethink what you are doing. Even more so if the tool in question refuses to do anything unless -f is given. That said, I'm glad to see that the OP took this as a learning experience and not as a reason for posting a long-winded rant about why git should be considered harmf…

I'd say rm -f may be the exception - technically you could run a chmod +w before but you'll end up at the same place

Re: Benefits of a Git-backed Blog

#13

Post by EnderMB »

Perhaps a bit off-topic, but isn't the use of post-receive hooks to publish your content effectively hacking Git to do something that it shouldn't?

For me, the ideal approach was always to use continuous integration to publish/build my site fresh every time I commit.

Re: Benefits of a Git-backed Blog

#14

Post by gravitronic »

antonyme wrote: post #8

I'm just about to switch over from MovableType to GitHub Pages http://pages.github.com/ . They use Jekyll http://jekyllrb.com/ to publish text, HTML or Markdown. So far it's pretty awesome. The benefits of this particular setup include: * all articles are under version control * just do a `push` to publish * easily run a local Jekyll server to preview articles * use a real programmer's text editor (not some web form)…

Oh hey, it's the article I expected to read when I clicked on the blog post

Re: Benefits of a Git-backed Blog

#15

Post by beothorn »

I'm beggining a github blog using jekyll. If anyone is interested, it is still a very basic and easy to understand setup. Also, I wrote a little script to write posts from the command line: https://github.com/beothorn/beothorn.github.com/blob/master/... Just change vim to your favorite editor.

Re: Benefits of a Git-backed Blog

#16

Post by jankins »

antonyme wrote: post #8

I'm just about to switch over from MovableType to GitHub Pages http://pages.github.com/ . They use Jekyll http://jekyllrb.com/ to publish text, HTML or Markdown. So far it's pretty awesome. The benefits of this particular setup include: * all articles are under version control * just do a `push` to publish * easily run a local Jekyll server to preview articles * use a real programmer's text editor (not some web form)…

Much more complete list than mine, ha. Pelican supports github pages as well, though I decided not to use github in order to learn git better -- which should have been the singular title of the article as it turns out ("benefit") but what the hell, sue me.

Re: Benefits of a Git-backed Blog

#17

Post by jankins »

EnderMB wrote: post #13

Perhaps a bit off-topic, but isn't the use of post-receive hooks to publish your content effectively hacking Git to do something that it shouldn't? For me, the ideal approach was always to use continuous integration to publish/build my site fresh every time I commit.

Not off-topic at all, I'd definitely like to hear more about this. I read a few 'use git to publish a live site' explanations, and settled on the post-receive hook because it was the first one to make sense to me and work, not because it's the ideal way to do it.
Post reply on HN